From mboxrd@z Thu Jan 1 00:00:00 1970 From: Manish Jaggi Subject: Re: RFC: [PATCH 1/3] Enhance platform support for PCI Date: Thu, 26 Feb 2015 15:39:55 +0530 Message-ID: <54EEF0F3.4050403@caviumnetworks.com> References: <54E71BDE.5020106@caviumnetworks.com> <54E7229C.7000301@linaro.org> <54E72452.3090801@caviumnetworks.com> <54E72688.9010005@linaro.org> <54E729F1.6000804@caviumnetworks.com> <54E73010.2050902@caviumnetworks.com> <1424439941.30924.243.camel@citrix.com> <54E74EA802000078000620B7@mail.emea.novell.com> <1424442385.30924.265.camel@citrix.com> <54E7552F020000780006215A@mail.emea.novell.com> <1424444504.30924.282.camel@citrix.com> <54E75D8702000078000621DD@mail.emea.novell.com> <1424453619.30924.381.camel@citrix.com> <54EAF6390200007800062593@mail.emea.novell.com> <1424695518.27930.74.camel@citrix.com> <54EB42320200007800062871@mail.emea.novell.com> <1424702013.27930.118.camel@citrix.com> <54EB4AFE02000078000628B3@mail.emea.novell.com> <1424703761.27930.140.camel@citrix.com> <54EB54D8020000780006296F@mail.emea.novell.com> <1424706397.27930.178.camel@citrix.com> <54EB61430200007800062AEA@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54EB61430200007800062AEA@mail.emea.novell.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: Jan Beulich , Ian Campbell Cc: Prasun.kapoor@cavium.com, Vijaya Kumar , Julien Grall , "StefanoStabellini(Stefano.Stabellini@citrix.com)" , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Monday 23 February 2015 09:50 PM, Jan Beulich wrote: >>>> On 23.02.15 at 16:46, wrote: >> On Mon, 2015-02-23 at 15:27 +0000, Jan Beulich wrote: >>>>>> On 23.02.15 at 16:02, wrote: >>>> Is the reason for the scan being of segment 0 only is that it is the one >>>> which lives at the legacy PCI CFG addresses (or those magic I/O ports)? >>> Right - ideally we would scan all segments, but we need Dom0 to >>> tell us which MMCFG regions are safe to access, >> Is this done via PHYSDEVOP_pci_mmcfg_reserved? > Yes. > >>> and hence can't >>> do that scan at boot time. But we also won't get away without >>> scanning, as we need to set up the IOMMU(s) to at least cover >>> the devices used for booting the system. >> Which hopefully are all segment 0 or aren't needed until after dom0 >> tells Xen about them I suppose. > Right. With EFI one may be able to overcome this one day, but the > legacy BIOS doesn't even surface mechanisms (software interrupts) > to access devices outside of segment 0. > >>> (All devices on segment zero are supposed to >>> be accessible via config space access method 1.) >> Is that "the legacy .... or magic ..." again? > Yes (just that there are two of them). Ian/Jan, Have you reached a conclusion? > Jan > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel