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

[Xen-devel] How console data travel in Xen?


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: NAHieu <nahieu@xxxxxxxxx>
  • Date: Fri, 1 Jul 2005 00:41:52 +0900
  • Delivery-date: Thu, 30 Jun 2005 15:40:44 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=jTBmcCYQ6qKWoY7JPGls+IPaSMaR2OBRYorafghjpbmI+OQkcGsFrhOYzWoT6MnIwkbaWgYeBLHGBkwSzRiZ7EpMBXoTedYfKJjKBuFNXlNBIcvOkXgoSvyfidO1CsNub9aW63GqqpXEByvEXKNCBnH3uSbK3LoTivARfilpuno=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hello,

I am trying to investigate in detail how console data go thru the Xen
system. Suppose that I am running a domainU, when I type at the
domainU console (I connect to the console with xencons or ssh), how
data (from keyboard in this case) travel from low level (hardware) to
Xen, then to dom0, then to domU?

I am not afraid of reading and hacking the source to understand this,
but I dont know where to start in the jungle of code. (Which files
should I pay attention to?)

Looks like xen/drivers/char/console.c is not related to this problem?

All the helps are highly appreciated ;-)

Thank you a lot,
Hieu

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


 


Rackspace

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