From: Chao Gao <chao.gao@intel.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
"Crawford Eric R" <Eric.R.Crawford@intel.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>, Tim Deegan <tim@xen.org>,
xen-devel@lists.xen.org, Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>
Subject: Re: [PATCH v7] VT-d: use correct BDF for VF to search VT-d unit
Date: Tue, 22 Aug 2017 16:48:03 +0800 [thread overview]
Message-ID: <20170822084800.GA7404@op-computing> (raw)
In-Reply-To: <20170822072958.u7uilbwg2wbgcgl3@MacBook-Pro-de-Roger.local>
On Tue, Aug 22, 2017 at 08:29:58AM +0100, Roger Pau Monné wrote:
>On Tue, Aug 22, 2017 at 05:52:04AM +0800, Chao Gao wrote:
>> When SR-IOV is enabled, 'Virtual Functions' of a 'Physical Function' are under
>> the scope of the same VT-d unit as the 'Physical Function'. A 'Physical
>> Function' can be a 'Traditional Function' or an ARI 'Extended Function'.
>> And furthermore, 'Extended Functions' on an endpoint are under the scope of
>> the same VT-d unit as the 'Traditional Functions' on the endpoint. To search
>> VT-d unit, the BDF of PF or the BDF of a traditional function may be used. And
>> it depends on whether the PF is an extended function or not.
>>
>> Current code uses PCI_SLOT() to recognize an ARI 'Extended Funcion'. But it
>> is problematic for a corner case (a RC endpoint with SRIOV capability
>> and has its own VT-d unit), leading to matching to a wrong VT-d unit.
>>
>> This patch reuses 'is_extfn' field in VF's struct pci_dev_info to indicate
>> whether the PF of this VF is an extended function. The field helps to use
>> correct BDF to search VT-d unit.
>>
>> Reported-by: Crawford, Eric R <Eric.R.Crawford@intel.com>
>> Signed-off-by: Chao Gao <chao.gao@intel.com>
>
>This looks fine to me:
>
>Reviewed-by: Roger Pau Monné <roger.pau@citrix.com>
>
Thank you, Roger.
>Given the issues we had before with this commit, could we please have
>a Tested-by by someone? I saw that you dropped Eric's, and I would
>like to have it again.
Hi, Eric.
Could you test this patch again and give this patch your Tested-by if it
passes your test?
Thanks
Chao
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-08-22 8:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 21:52 [PATCH v7] VT-d: use correct BDF for VF to search VT-d unit Chao Gao
2017-08-22 7:29 ` Roger Pau Monné
2017-08-22 8:48 ` Chao Gao [this message]
2017-08-22 12:43 ` Jan Beulich
2017-08-23 1:05 ` Chao Gao
2017-08-23 7:16 ` Roger Pau Monné
2017-08-23 7:20 ` Jan Beulich
2017-08-23 7:31 ` Roger Pau Monné
2017-08-23 6:46 ` Chao Gao
2017-08-23 8:01 ` Roger Pau Monné
2017-08-23 7:42 ` Chao Gao
2017-08-23 8:52 ` Jan Beulich
2017-08-24 7:29 ` Tian, Kevin
2017-08-23 8:00 ` Jan Beulich
2017-08-23 8:04 ` Jan Beulich
2017-08-23 7:39 ` Chao Gao
2017-08-23 8:51 ` Jan Beulich
2017-08-24 7:22 ` Tian, Kevin
[not found] ` <AADFC41AFE54684AB9EE6CBC0274A5D190D80DD6@SHSMSX101.ccr.corp.intel.com>
2017-08-24 8:01 ` Tian, Kevin
2017-08-24 8:22 ` Jan Beulich
2017-08-24 9:36 ` Chao Gao
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=20170822084800.GA7404@op-computing \
--to=chao.gao@intel.com \
--cc=Eric.R.Crawford@intel.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=kevin.tian@intel.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/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).