From: Gordan Bobic <gordan@bobich.net>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Santosh.Jodh@citrix.com, linux-kernel@vger.kernel.org,
yuval.shaia@oracle.com, xhejtman@ics.muni.cz,
David Vrabel <david.vrabel@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Bjorn Helgaas <bhelgaas@google.com>,
boris.ostrovsky@oracle.com
Subject: Re: [v1 1/2] xen/p2m: Create identity mappings for PFNs beyound E820 and PCI BARs
Date: Tue, 29 Oct 2013 15:59:53 +0000 [thread overview]
Message-ID: <e59174616cf59e286cb950ce31c72928@mail.shatteredsilicon.net> (raw)
In-Reply-To: <20131029151129.GA20984@phenom.dumpdata.com>
On Tue, 29 Oct 2013 11:11:29 -0400, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Tue, Oct 29, 2013 at 02:55:13PM +0000, Jan Beulich wrote:
>> >>> On 29.10.13 at 15:45, Konrad Rzeszutek Wilk
>> <konrad.wilk@oracle.com> wrote:
>> > On Tue, Oct 29, 2013 at 08:23:30AM +0000, Jan Beulich wrote:
>> >> >>> On 28.10.13 at 17:58, Konrad Rzeszutek Wilk
>> <konrad.wilk@oracle.com> wrote:
>> >> > On Fri, Oct 25, 2013 at 04:08:19PM -0600, Bjorn Helgaas wrote:
>> >> >> If you can look at PCI host bridge apertures instead of BARs,
>> that
>> >> >> would solve both problems. Reassigning those apertures is
>> >> >> theoretically possible but is not even a gleam in our eyes
>> yet.
>> >> >
>> >> > <nods> I think I have to have both (BARs and host bridge
>> apertures) as when
>> >> > we do PCI passthrough to a guest - we might do it without a
>> bridge.
>> >>
>> >> Why? Aren't the host bridge ranges necessarily a superset of the
>> >> individual devices' BARs?
>> >
>> > Yes. But when you pass in a PCI device to a PV guest you don't
>> pass in the
>> > bridge. Just the PCI device itself.
>>
>> Right you are. Which means that basing the whole logic on the
>> PCI device BARs is likely wrong anyway, not just because it
>> doesn't account for other MMIO ranges.
>
> Right, but that is OK. When you pass in a PCI device to a PV guest
> you
> only care about that specific device driver being able to access its
> BARs.
Maybe I'm reading this wrong, but my understanding is that you cannot
pass PCI bridges to domU anyway (in HVM - I tried). Is that not the
case?
I'm particularly interested in this for two reasons:
1) Some GPUs (Nvidia?) use bus resets to reset the GPU
2) Multi-GPU cards (e.g. GTX690/Grid K2) come with a PCIe bridge
of their own. I am successfully passing a modified GTX680 (as either
a Grid K2 or Quadro K5000) to a domU, but have completely failed to
get a modified GTX690 (Grid K2, exact same GPU as the GTX680) to work
with passthru. The only theory I have is that the extra PCIe bridge
is the problem (possibly a compound problem that only manigests when
there is a PLX (as per GTX690) PCIe bridge behind a NF200 PCIe bridge,
behind an Intel PCIe bridge.
Gordan
next prev parent reply other threads:[~2013-10-29 15:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-25 15:03 [PATCH v1] Set 1-1 P2M for PCI BARs and MCFG regions - if needed Konrad Rzeszutek Wilk
2013-10-25 15:03 ` [v1 1/2] xen/p2m: Create identity mappings for PFNs beyound E820 and PCI BARs Konrad Rzeszutek Wilk
2013-10-25 16:38 ` Konrad Rzeszutek Wilk
2013-10-25 22:08 ` Bjorn Helgaas
2013-10-28 9:51 ` Jan Beulich
2013-10-28 16:58 ` Konrad Rzeszutek Wilk
2013-10-29 8:23 ` Jan Beulich
2013-10-29 14:45 ` Konrad Rzeszutek Wilk
2013-10-29 14:55 ` Jan Beulich
2013-10-29 15:11 ` Konrad Rzeszutek Wilk
2013-10-29 15:30 ` Jan Beulich
2013-10-29 15:59 ` Gordan Bobic [this message]
2013-10-25 15:03 ` [v1 2/2] xen/mcfg: Call PHYSDEVOP_pci_mmcfg_reserved for MCFG areas and setup 1-1 P2M Konrad Rzeszutek Wilk
2013-10-25 22:58 ` [Xen-devel] [PATCH v1] Set 1-1 P2M for PCI BARs and MCFG regions - if needed David Vrabel
2013-10-25 23:39 ` Konrad Rzeszutek Wilk
2013-10-28 16:52 ` Konrad Rzeszutek Wilk
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=e59174616cf59e286cb950ce31c72928@mail.shatteredsilicon.net \
--to=gordan@bobich.net \
--cc=JBeulich@suse.com \
--cc=Santosh.Jodh@citrix.com \
--cc=bhelgaas@google.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xensource.com \
--cc=xhejtman@ics.muni.cz \
--cc=yuval.shaia@oracle.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).