All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: NAHieu <nahieu@gmail.com>, xen-devel <xen-devel@lists.xensource.com>
Subject: Re: How console data travel in Xen?
Date: Thu, 30 Jun 2005 13:39:22 -0500	[thread overview]
Message-ID: <42C43C5A.6040808@us.ibm.com> (raw)
In-Reply-To: <5d7aca95050630113550c453b0@mail.gmail.com>

NAHieu wrote:

>Oops, probably you missed my point: I want to know how the data go
>from low level (HW) to Xen (hypervisor), then to dom0.
>  
>
I was avoiding answering this because I'm sure that someone who's much 
smarter than me is going to jump in and correct me on this :-)

dom0 takes the keyboard interrupts just like it normally would.  I 
believe (and I may be wrong here) that in x86 the IDT is setup such that 
keyboard interrupts go directly to the dom0 kernel (since it's in ring 1).

I would imagine that in x86-64 that those interrupts have to be 
reflected back down to the guest OS.  This is almost pure speculation 
though so hopefully someone else will jump in and correct me.

>I guess it works this way: dom0 has privileged right to access to HW,
>so it can take keyboard code directly (I guess it goes thru Xen, but
>dont know exactly how?). Then from dom to domU, it works like you
>explained. Is that correct?
>
>Many thanks, Anthony.
>Hieu.
>
>  
>

  parent reply	other threads:[~2005-06-30 18:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 15:41 How console data travel in Xen? NAHieu
2005-06-30 16:08 ` 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 [this message]
  -- 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=42C43C5A.6040808@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=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.