From: NAHieu <nahieu@gmail.com>
To: xen-devel@lists.xensource.com
Subject: How console data travel in Xen?
Date: Fri, 1 Jul 2005 00:41:52 +0900 [thread overview]
Message-ID: <5d7aca950506300841306bad7a@mail.gmail.com> (raw)
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
next reply other threads:[~2005-06-30 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 15:41 NAHieu [this message]
2005-06-30 16:08 ` How console data travel in Xen? Anthony Liguori
2005-06-30 17:28 ` NAHieu
2005-06-30 18:16 ` Anthony Liguori
[not found] ` <5d7aca95050630113550c453b0@mail.gmail.com>
2005-06-30 18:39 ` Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2005-06-30 15:52 Li, Xin B
2005-06-30 9:06 NAHieu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5d7aca950506300841306bad7a@mail.gmail.com \
--to=nahieu@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.