From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: RFC: [PATCH 1/3] Enhance platform support for PCI Date: Fri, 27 Feb 2015 15:29:37 +0000 Message-ID: <1425050977.14641.237.camel@citrix.com> References: <1425048166.14641.217.camel@citrix.com> <1425050679.14641.233.camel@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1425050679.14641.233.camel@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: Stefano Stabellini Cc: Prasun.kapoor@cavium.com, Manish Jaggi , Vijaya Kumar , Julien Grall , xen-devel@lists.xen.org, "StefanoStabellini(Stefano.Stabellini@citrix.com)" , Jan Beulich List-Id: xen-devel@lists.xenproject.org On Fri, 2015-02-27 at 15:24 +0000, Ian Campbell wrote: > In Linux dom0 we call it walking pci_mmcfg_list, which looking at > arch/x86/pci/mmconfig-shared.c pci_parse_mcfg is populated by walking > over a "struct acpi_table_mcfg" BTW according to http://lists.linaro.org/pipermail/fw-summit/2015-January/000070.html: MCFG Signature Reserved (signature == "MCFG") == Memory-mapped ConFiGuration space == If the platform supports PCI/PCIe, an MCFG table is required. Which for ACPI systems at least we can also parse in Xen. The contents is in "PCI Firmware Specification, Revision 3.0" which I don't have a copy of handy. Ian.