From: "Jan Beulich" <jbeulich@novell.com>
To: Dexuan Cui <dexuan.cui@intel.com>
Cc: xen-devel@lists.xensource.com
Subject: co-assignment needs for PCI devices
Date: Tue, 31 Mar 2009 08:10:07 +0100 [thread overview]
Message-ID: <49D1DDEF.76E4.0078.0@novell.com> (raw)
c/s 18046 adds the requirement to co-assign PCI devices behind bridges/
PCIe functions on the same device when the (perhaps individual) device/
function intended to be assigned doesn't support FLR and doesn't sit on
bus 0. For non-IOMMU environments (which are insecure anyway) this
could be considered a regression, since passing through individual devices/
functions didn't know such a restriction earlier.
Also, being not really knowledgeable about all the differences between
PCIe and PCI, I'd appreciate some clarification on why on PCIe it is
possible and correct to do a secondary bus reset when targeting just
the (PCIe) functions of a single device - to me this seems to imply that
there's a one-device-per-non-root-bus restriction there.
Thanks, Jan
next reply other threads:[~2009-03-31 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 7:10 Jan Beulich [this message]
2009-03-31 7:48 ` co-assignment needs for PCI devices Cui, Dexuan
2009-03-31 7:57 ` Jan Beulich
2009-03-31 8:10 ` Cui, Dexuan
2009-03-31 12:21 ` Ross Philipson
2009-04-01 8:20 ` Cui, Dexuan
2009-04-01 13:09 ` Ross Philipson
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=49D1DDEF.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=dexuan.cui@intel.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 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.