All of lore.kernel.org
 help / color / mirror / Atom feed
From: Himanshu Raj <rhim@cc.gatech.edu>
To: "Mike D. Day" <ncmike@us.ibm.com>
Cc: Xen Mailing List <xen-devel@lists.xensource.com>
Subject: Re: driver domains
Date: Tue, 18 Jul 2006 18:41:33 -0400	[thread overview]
Message-ID: <20060718224133.GI28405@cc.gatech.edu> (raw)
In-Reply-To: <44BD293B.8010306@us.ibm.com>

Hi Mike,

Interrupts are passed on to the domain that registers the irq handler (and
only priviledged domains are allowed to do so). Hence the interrupt would be
sent directly to driver domain (unless it is being shared by multiple domains,
in which case it would go to all the domains).

A good start would be to look at xen/arch/x86/irq.c, specifically at pirq_guest_bind,
pirq_guest_unbind and __do_IRQ_guest.

HTH,
-Himanshu

On Tue, Jul 18, 2006 at 02:32:27PM -0400, Mike D. Day wrote:
> For a driver domain, do interrupts for the devices that service that 
> domain get handled by the driver domain itself, or by domain 0 first?
> 
> Which code should I read to understand how this works?
> 
> thanks,
> 
> Mike Day
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel

-- 
-------------------------------------------------------------------------
Himanshu Raj
PhD Student, GaTech (www.cc.gatech.edu/~rhim)
I prefer to receive attachments in an open, non-proprietary format.
-------------------------------------------------------------------------

  reply	other threads:[~2006-07-18 22:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 18:32 driver domains Mike D. Day
2006-07-18 22:41 ` Himanshu Raj [this message]
2006-07-18 23:10   ` Mike D. Day
  -- strict thread matches above, loose matches on Subject: below --
2006-07-18 22:42 Ian Pratt
2006-01-25 18:24 Muli Ben-Yehuda
2006-01-25 18:49 ` Keir Fraser
2006-01-25 21:10   ` Jon Mason
2004-05-25 13:55 valerie galey

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=20060718224133.GI28405@cc.gatech.edu \
    --to=rhim@cc.gatech.edu \
    --cc=ncmike@us.ibm.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.