From: Simon Horman <horms@verge.net.au>
To: Gianni Tedesco <gianni.tedesco@citrix.com>
Cc: Xen Devel <xen-devel@lists.xensource.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH]: xl: pci multi-function passthrough v2
Date: Mon, 9 Aug 2010 16:27:03 -0400 [thread overview]
Message-ID: <20100809202703.GL17141@verge.net.au> (raw)
In-Reply-To: <1281355239.18490.259.camel@qabil.uk.xensource.com>
On Mon, Aug 09, 2010 at 01:00:39PM +0100, Gianni Tedesco wrote:
> Changes since last time:
> 1. Incorporate Stefanos feedback wrt. coding style, commenting
> non-obvious code and making single-function a special-case of
> multi-function
> 2. Also fix the case for passing through a single sub-function and
> re-mapping it as a single-function virtual device. (ie: pfunc =
> non-zero, vfunc = zero). Apparently needed for SR-IOV.
> 3. One-liner format change in xl pci-list-assignable to make it
> print a copy-and-pasteable BDF.
> 8<----------------------------------------
>
> Implement PCI pass-through for multi-function devices. The supported BDF
> notation is: BB:DD.* - therefore passing-through a subset of functions or
> remapping the function numbers is not supported except for when passing
> through a single function which will be a virtual function 0.
Is there any plan to extend this to allow for re-mapping and the like.
When I worked on the original multi-function support (last year)
this seemed to be a requirement of some people.
next prev parent reply other threads:[~2010-08-09 20:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 12:00 [PATCH]: xl: pci multi-function passthrough v2 Gianni Tedesco
2010-08-09 12:47 ` Gianni Tedesco
2010-08-09 16:47 ` Stefano Stabellini
2010-08-09 20:27 ` Simon Horman [this message]
2010-08-10 11:25 ` Gianni Tedesco
2010-08-10 15:25 ` Simon Horman
2010-08-10 15:31 ` Gianni Tedesco
2010-08-10 16:00 ` Simon Horman
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=20100809202703.GL17141@verge.net.au \
--to=horms@verge.net.au \
--cc=Ian.Jackson@eu.citrix.com \
--cc=gianni.tedesco@citrix.com \
--cc=stefano.stabellini@eu.citrix.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).