From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, Jeremy Fitzhardinge <jeremy@goop.org>
Subject: PV PCI passthrough - summary/status
Date: Mon, 26 Oct 2009 11:03:21 -0400 [thread overview]
Message-ID: <20091026150321.GA6969@phenom.dumpdata.com> (raw)
There has been a sudden flurry of folks using the PCI pass-through and I thought
this would be a good time to give an update on its status in the PV OPS side.
Please keep in mind this is for PV guests, not HVM (well, kind of - there is one
overlap - BAR page alignment).
There are four outstanding issues:
- MSI support (No API for pci-back to pass the domain ID to Xen's Dom0 MSI support:
xen_setup_msi_irq). One idea I am slowly prototyping is for xen_create_msi_irq
to enumerate the XenStore keys and see if the PCI device in question also
residies in /local/domain/0/pci/X/Y/ and extract the domain ID from that.
The beauty of this is that it can also be used by the Xen-SWIOTLB to determine
whether it should turn itself on for DomU guests.
- PCI front support. Haven't started on this.
- BAR page alignment. Looking to see if Xen/xc.c can handle mapping of
a offset within a page. This way this requirment (need a page-aligned BAR)
can be eliminated. Or if this is a no-go see if there is a security risk
in passing the whole page to the guest. Lastly if none of this works, revisit
the 2.6.18 'reassign_resources' patch that sets the BARs to page-aligned addresses.
- Bug #1340: The Function Level Reset reset requires that PCI devices behind a bridge
be owned by the same guest. Based on the comments, without the FLR capability in 3.2, the
PCI devices worked fine. We could provie a 'flr_inhibit' flag which would revert
back to 3.2 and not do an FLR?
Any suggestions, etc., are much welcome.
reply other threads:[~2009-10-26 15:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20091026150321.GA6969@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=jeremy@goop.org \
--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.