From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Jan Beulich <JBeulich@novell.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Rzeszutek Wilk <konrad.wilk@oracle.com>,
Konrad
Subject: Re: granting access to MSI-X table and pending bit array
Date: Fri, 9 Jul 2010 10:59:20 +0100 [thread overview]
Message-ID: <C85CB188.1A2B5%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4C370DDF020000780000A718@vpn.id2.novell.com>
On 09/07/2010 10:54, "Jan Beulich" <JBeulich@novell.com> wrote:
> With the revert mentioned above being about PV guests, I wonder
> what problems PV guests had with not being able to access the
> table and PBA ranges. Linux doesn't (so far) use the PBA at all,
> and according to my analysis of drivers/pci/msi-xen.c also doesn't
> access the table in any way even when being run privileged. Keir,
> with the description of c/s 20171 being rather brief - what was
> the problem PV guests were having? Or was that more specifically
> with stubdom wanting to do above mentioned writes on behalf of
> the serviced guest?
I was trying to pass through an Intel ixgbe VF to a PV guest. The guest
driver attempts to map some resource range (I think indicated via a BAR) and
that fails because one page in the range is disallowed, corresponding to an
MSI-X iomem page. Reverting this patch made things work. :-) Perhaps a dummy
page should get silently mapped in or something, but I didn't investigate
further myself.
-- Keir
next prev parent reply other threads:[~2010-07-09 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 10:14 granting access to MSI-X table and pending bit array Jan Beulich
2010-07-07 14:14 ` Konrad Rzeszutek Wilk
2010-07-07 14:31 ` Jan Beulich
2010-07-07 16:49 ` Stefano Stabellini
2010-07-09 9:54 ` Jan Beulich
2010-07-09 9:59 ` Keir Fraser [this message]
2010-07-12 9:55 ` Jan Beulich
2010-07-15 8:22 ` Jiang, Yunhong
-- strict thread matches above, loose matches on Subject: below --
2010-08-05 17:44 Jan Beulich
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=C85CB188.1A2B5%keir.fraser@eu.citrix.com \
--to=keir.fraser@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--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).