All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Ross Lagerwall <ross.lagerwall@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH] xen/pci: Try harder to get PXM information for Xen
Date: Wed, 8 Apr 2015 17:44:27 +0100	[thread overview]
Message-ID: <55255AEB.4090401@citrix.com> (raw)
In-Reply-To: <552534D3.9090806@oracle.com>

On 08/04/15 15:01, Boris Ostrovsky wrote:
> On 04/08/2015 09:39 AM, Ross Lagerwall wrote:
>> If the device being added to Xen is not contained in the ACPI table,
>> walk the PCI device tree to find a parent that is contained in the ACPI
>> table before finding the PXM information from this device.
>>
>> Signed-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>
>> ---
>>   drivers/xen/pci.c | 15 +++++++++++++--
>>   1 file changed, 13 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/xen/pci.c b/drivers/xen/pci.c
>> index 95ee430..6837181 100644
>> --- a/drivers/xen/pci.c
>> +++ b/drivers/xen/pci.c
>> @@ -19,6 +19,7 @@
>>     #include <linux/pci.h>
>>   #include <linux/acpi.h>
>> +#include <linux/pci-acpi.h>
>>   #include <xen/xen.h>
>>   #include <xen/interface/physdev.h>
>>   #include <xen/interface/xen.h>
>> @@ -67,8 +68,18 @@ static int xen_add_device(struct device *dev)
>>     #ifdef CONFIG_ACPI
>>           handle = ACPI_HANDLE(&pci_dev->dev);
>> -        if (!handle && pci_dev->bus->bridge)
>> -            handle = ACPI_HANDLE(pci_dev->bus->bridge);
>> +        if (!handle) {
>> +            /*
>> +             * This device was not listed in the ACPI name space at
>> +             * all. Try to get acpi handle of parent pci bus.
>> +             */
>> +            struct pci_bus *pbus;
>> +            for (pbus = pci_dev->bus; pbus; pbus = pbus->parent) {
>> +                handle = acpi_pci_get_bridge_handle(pbus);
>> +                if (handle)
>> +                    break;
>> +            }
>> +        }
>>   #ifdef CONFIG_PCI_IOV
>>           if (!handle && pci_dev->is_virtfn)
>>               handle = ACPI_HANDLE(physfn->bus->bridge);
> 
> 
> Shouldn't we first look at physfn, before going up the tree?

That sounds sensible but should be a separate pre-requisite patch.

David

  reply	other threads:[~2015-04-08 16:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-08 13:39 [PATCH] xen/pci: Try harder to get PXM information for Xen Ross Lagerwall
2015-04-08 14:01 ` Boris Ostrovsky
2015-04-08 16:44   ` David Vrabel [this message]
2015-04-08 17:17     ` Boris Ostrovsky
2015-04-08 17:57       ` David Vrabel
2015-04-09  6:55       ` Ross Lagerwall

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=55255AEB.4090401@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=ross.lagerwall@citrix.com \
    --cc=xen-devel@lists.xenproject.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 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.