RE: [Xen-ia64-devel] [PATCH] console

["Tian, Kevin" <kevin.tian@xxxxxxxxx>]

>From: Tristan Gingold
>Sent: 2005年11月3日 0:46
>
>Hi,
>
>here is a small patch which fixes the rejected patch during kernel compilation
>and a bug in evtchn_ia64.c
>
>I am now able to use xencons:
>* do not config serial port in linux
>* use 'console=ttyS0' in xen-linux command line.

This is absolutely a good patch. Previously I also saw "WARNING: failed to 
register Xen virtual console driver as ..." for dom0, but I worked around it by 
compiling CONFIG_VT and SERIAL_CONSOLE into dom0 kernel. Then by assigning both 
tty0 and ttyS0 as the default console in cmdline, I can see serial output from 
dom0 since dom0 owns the serial port completely. But that's not the right 
answer obviously since Xen lost control upon serial port, and user can't use 
debug command to track Xen status. So your patch actually gives the issue a 
good start.

A small comment is that bind_virq_to_evtchn is a stale interface none used now. 
So Dan, you can remove that interface when check-in Tristan's patch.

>Note: without more modifs, xenconsole is output only.
>
>
>Signed-off-by Tristan Gingold <tristan.gingold@xxxxxxxx>
>
>Thanks,
>Tristan.

Actually up to this point, I begin to understand your concern about irq 
virtualization raised before. ;-) IMO, first we need change Xen to register 
interrupt handler for serial input interrupt like adding a serial_init_postirq. 
Regarding xenlinux side, maybe we don't need change anything. Currently the 
VIRQ_CONSOLE is bound to event. And once Xen gets control upon serial port, 
current serial driver in xen will send VIRQ_CONSOLE to dom0 in receive handler. 
In that case, xenconsole can still get input by event notification. How do you 
think?

Thanks,
Kevin

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