From: George Dunlap <george.dunlap@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: [PATCH] xen/pci: make bus notifier handler return sane values
Date: Thu, 25 Aug 2011 10:14:18 +0100 [thread overview]
Message-ID: <1314263659.29585.7353.camel@elijah> (raw)
In-Reply-To: <20110824204241.GC27865@dumpdata.com>
On Wed, 2011-08-24 at 21:42 +0100, Konrad Rzeszutek Wilk wrote:
> > Requiring the PCI device to be known to Xen to be able to use MSI is
> > an implementation detail of the hypervisor. And in fact I had a patch
> > to remove the call to pci_get_pdev() from map_domain_pirq() (since
> > setup_msi_irq() doesn't really consume this parameter). This got made
> > impossible to do (at least for the moment) with George's
> > 23753:2e0cf9428554 (and later on the device is getting looked up by
> > __pci_enable_msi{,x}() anyway, but even that is an implementation
> > choice, not a hard requirement afaict).
The device has to be known to Xen in order to do proper interrupt
remapping, does it not? At least if the AMD per-device interrupt
remapping tables.
I suppose if you really wanted to, we could refactor the code so that
the time Xen needed to know devices for IRQs coincided exactly with when
Xen needs to know devices for IOMMUs. I don't understand the motivation
for such a requirement yet.
-George
next prev parent reply other threads:[~2011-08-25 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 8:32 [PATCH] xen/pci: make bus notifier handler return sane values Jan Beulich
2011-08-17 14:57 ` Konrad Rzeszutek Wilk
2011-08-17 15:18 ` Jan Beulich
2011-08-17 15:31 ` Konrad Rzeszutek Wilk
2011-08-17 15:37 ` Jan Beulich
2011-08-22 16:20 ` Konrad Rzeszutek Wilk
2011-08-23 8:19 ` Jan Beulich
2011-08-24 20:42 ` Konrad Rzeszutek Wilk
2011-08-25 9:14 ` George Dunlap [this message]
2011-08-25 10:07 ` Jan Beulich
2011-08-25 10:15 ` George Dunlap
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=1314263659.29585.7353.camel@elijah \
--to=george.dunlap@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).