From: Wei Yang <richard.weiyang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Alex Williamson
<alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
jroedel-l3A5Bk7waGM@public.gmane.org
Subject: Re: [PATCH] iommu: narrow the search range by iterating on current bus
Date: Fri, 5 Aug 2016 14:03:17 +0000 [thread overview]
Message-ID: <20160805140317.GA26921@vultr.guest> (raw)
In-Reply-To: <20160728090132.42c6ebc1-1yVPhWWZRC1BDLzU/O5InQ@public.gmane.org>
On Thu, Jul 28, 2016 at 09:01:32AM -0600, Alex Williamson wrote:
>On Thu, 28 Jul 2016 14:52:59 +0000
>Wei Yang <richard.weiyang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>> According to the comments and code, get_pci_function_alias_group() and
>> get_pci_alias_group() do the search on the same pci bus. This means we can
>> just iterate on the bus the pci device attaches to.
>>
>> This patch narrows the search range by just iterating on the current bus
>> and fix one typo in comment.
>>
>> Signed-off-by: Wei Yang <richard.weiyang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> ---
>> drivers/iommu/iommu.c | 22 ++++++++--------------
>> 1 file changed, 8 insertions(+), 14 deletions(-)
>>
>> diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iommu.c
>> index 3000051..0338a81 100644
>> --- a/drivers/iommu/iommu.c
>> +++ b/drivers/iommu/iommu.c
>> @@ -643,17 +643,15 @@ static struct iommu_group *get_pci_function_alias_group(struct pci_dev *pdev,
>> if (!pdev->multifunction || pci_acs_enabled(pdev, REQ_ACS_FLAGS))
>> return NULL;
>>
>> - for_each_pci_dev(tmp) {
>> - if (tmp == pdev || tmp->bus != pdev->bus ||
>> + list_for_each_entry(tmp, &pdev->bus->devices, bus_list) {
>
>I believe this was using for_each_pci_dev() exactly because it takes a
>reference to the device and therefore we can use it to get a reference
>to the group. How do you justify removing these reference semantics?
>Thanks,
>
Alex,
With some investigation, I believe these reference are important. Thanks for
reminding.
Well, the pci_dev and the bus->devices list are protected by pci_bus_sem and
we have already had a function to walk the pci bus safely by holding this
semaphore. While the pci_walk_bus() will continue the process when it sees a
bridge device.
So I create another patch to export a function to walk just on the local bus
and then calling this from get_pci_function_alias_group() and
get_pci_alias_group().
Since this change is related to pci subsystem, I include Bjorn.
Hi, Bjorn,
Haven't seen you for a long time. Hope you would like the idea.
>Alex
>
>> + if (tmp == pdev ||
>> PCI_SLOT(tmp->devfn) != PCI_SLOT(pdev->devfn) ||
>> pci_acs_enabled(tmp, REQ_ACS_FLAGS))
>> continue;
>>
>> group = get_pci_alias_group(tmp, devfns);
>> - if (group) {
>> - pci_dev_put(tmp);
>> + if (group)
>> return group;
>> - }
>> }
>>
>> return NULL;
>> @@ -681,23 +679,19 @@ static struct iommu_group *get_pci_alias_group(struct pci_dev *pdev,
>> if (group)
>> return group;
>>
>> - for_each_pci_dev(tmp) {
>> - if (tmp == pdev || tmp->bus != pdev->bus)
>> + list_for_each_entry(tmp, &pdev->bus->devices, bus_list) {
>> + if (tmp == pdev)
>> continue;
>>
>> /* We alias them or they alias us */
>> if (pci_devs_are_dma_aliases(pdev, tmp)) {
>> group = get_pci_alias_group(tmp, devfns);
>> - if (group) {
>> - pci_dev_put(tmp);
>> + if (group)
>> return group;
>> - }
>>
>> group = get_pci_function_alias_group(tmp, devfns);
>> - if (group) {
>> - pci_dev_put(tmp);
>> + if (group)
>> return group;
>> - }
>> }
>> }
>>
>> @@ -794,7 +788,7 @@ struct iommu_group *pci_device_group(struct device *dev)
>>
>> /*
>> * Look for existing groups on non-isolated functions on the same
>> - * slot and aliases of those funcions, if any. No need to clear
>> + * slot and aliases of those functions, if any. No need to clear
>> * the search bitmap, the tested devfns are still valid.
>> */
>> group = get_pci_function_alias_group(pdev, (unsigned long *)devfns);
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2016-08-05 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 14:52 [PATCH] iommu: narrow the search range by iterating on current bus Wei Yang
[not found] ` <1469717579-8244-1-git-send-email-richard.weiyang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-07-28 15:01 ` Alex Williamson
[not found] ` <20160728090132.42c6ebc1-1yVPhWWZRC1BDLzU/O5InQ@public.gmane.org>
2016-08-05 13:47 ` [PATCH 1/2] PCI: add a function to walk on local bus Wei Yang
[not found] ` <1470404867-26783-1-git-send-email-richard.weiyang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-08-05 13:47 ` [PATCH 2/2] iommu: narrow the search range by iterating on current bus Wei Yang
2016-08-05 14:03 ` Wei Yang [this message]
[not found] ` <20160805140317.GA26921-yrDqe6+Pica9sAcnBtTtJQ@public.gmane.org>
2016-08-18 23:00 ` [PATCH] " Wei Yang
[not found] ` <20160818230026.GA2631-yrDqe6+Pica9sAcnBtTtJQ@public.gmane.org>
2016-09-28 19:51 ` Wei Yang
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=20160805140317.GA26921@vultr.guest \
--to=richard.weiyang-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=alex.williamson-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=bhelgaas-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=jroedel-l3A5Bk7waGM@public.gmane.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).