From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Thomas Pfeuffer <thomas.pfeuffer@mytum.de>
Cc: xen-devel@lists.xensource.com, mark.hurenkamp@xs4all.nl,
thomas@schwinge.name
Subject: Re: Question on pci-passthrough and event delivery
Date: Thu, 8 Apr 2010 10:03:16 -0400 [thread overview]
Message-ID: <20100408140316.GB29832@phenom.dumpdata.com> (raw)
In-Reply-To: <4BBD9843.60903@mytum.de>
On Thu, Apr 08, 2010 at 10:48:03AM +0200, Thomas Pfeuffer wrote:
> Hello,
>
> I am using pci-passthrough mechanism in Xen 3.4.2-rc2 to passthrough the
> only Network Interface Card to a pv driver domain.
>
> I have observed in xentrace output, that everytime a network packet
> arrives, the Xen hypervisor delivers an event to the driver domain and
> to dom0. I would think, that it is not neccassary to inform dom0, since
> only the driver domain has access to the NIC.
>
> Why is the interrupt from the NIC delivered to dom0 via an event, too?
The primary reason is that the SHARED_IRQ flag is set for the IRQ so
Xen delievers the IRQ to both Dom0 and the DomU which has the PCI device.
This is neccessary when there are more than one device sharing the same
IRQ (and they are in different domains). For situations in which there
is only device using the IRQ, this isn't neccessary - in fact, I think
this might be the bug that has been plaguing some users.
> Is it neccassary for pciback in dom0?
No. The events between PCI back and PCI front are via their own little
mechanism and it is only be used when a PCI device writes configuration
data or changes some state. Normal opperations, should not trigger this.
prev parent reply other threads:[~2010-04-08 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 8:48 Question on pci-passthrough and event delivery Thomas Pfeuffer
2010-04-08 14:03 ` Konrad Rzeszutek Wilk [this message]
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=20100408140316.GB29832@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=mark.hurenkamp@xs4all.nl \
--cc=thomas.pfeuffer@mytum.de \
--cc=thomas@schwinge.name \
--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.