From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: [PATCH v2] xen/pci: Try harder to get PXM information for Xen Date: Thu, 9 Apr 2015 09:42:25 +0100 Message-ID: <55263B71.7030604@citrix.com> References: <1428563110-18149-1-git-send-email-ross.lagerwall@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Yg82f-0000jv-UA for xen-devel@lists.xenproject.org; Thu, 09 Apr 2015 08:42:30 +0000 In-Reply-To: <1428563110-18149-1-git-send-email-ross.lagerwall@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ross Lagerwall , xen-devel@lists.xenproject.org Cc: Boris Ostrovsky , David Vrabel List-Id: xen-devel@lists.xenproject.org On 09/04/15 08:05, 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. > > Previously, it would try to get a handle for the device, then the > device's bridge, then the physfn. This changes the order so that it > tries to get a handle for the device, then the physfn, the walks up the > PCI device tree. Applied to devel/for-linus-4.1, thanks. David