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

[Xen-ia64-devel] RE: [PATCH] fixed serial console support


  • To: "Williamson, Alex (Linux Kernel Dev)" <alex.williamson@xxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Thu, 1 Dec 2005 10:05:34 -0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 01 Dec 2005 18:05:52 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcX2kamcyM00NmymSzioR69ve9KiFQAD4YNw
  • Thread-topic: [PATCH] fixed serial console support

>    It really seems like we need some way to hide individual 
> devices.

That would be a good general solution.  But Xen is not
interested in most devices so hiding the console is
a good first step.

> would only feel comfortable hiding a UART using "running_on_xen" for
> guest domain if we could do it such that only the console UART is
> hidden.  

Agreed

> Maybe it could be done via an "ignore_uart=" boot parameter
> passed into dom0(?)  

This would be fine too.  We just need to be able to select
dynamically at runtime what CONFIG_SERIAL_8250=n does at
compile time.

> >  Also,
> > will this eliminate the need to have CONFIG_VT=y
> > on dom0 and CONFIG_VT=n on domU?
> 
>    I don't know, I never really understood the problem there.  Xen
> provides a ttyS (serial) console device to dom0  and a tty (vt) device
> to non-dom0 domains.  I would therefore have expected domU to need
> CONFIG_VT=y.  What was the problem with CONFIG_VT on domU before?
> Thanks,

Tristan or Matt, do you know?

Thanks,
Dan

_______________________________________________
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®.