[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] PATCH: optionnaly enable xen console withirq/input.


  • To: "Williamson, Alex (Linux Kernel Dev)" <alex.williamson@xxxxxx>, "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Thu, 22 Jun 2006 10:57:07 -0700
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 22 Jun 2006 10:57:39 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcaV+PGZap8epoP3Qu+7BaBDsc5hZQALCaVQ
  • Thread-topic: [Xen-ia64-devel] PATCH: optionnaly enable xen console withirq/input.

>    I also don't agree that the Xen keytable is only for 
> developers.  It
> may be that this is an important debugging tool and therefore required
> to be able to support a real customer.  I'd rather see this feature on
> by default so it's there for in-the-field debugging later, and so that
> the xen/ia64 community uses it and makes sure it works.  Thanks,

You may want to ask about this in xen-devel.  Long
ago iirc there was some concern expressed that the
keytable might present possible security holes (maybe
DoS attacks)?

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.