Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758094Ab3J2PMK (ORCPT ); Tue, 29 Oct 2013 11:12:10 -0400 Received: from aserp1040.oracle.com ([141.146.126.69]:41352 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753742Ab3J2PMI (ORCPT ); Tue, 29 Oct 2013 11:12:08 -0400 Date: Tue, 29 Oct 2013 11:11:29 -0400 From: Konrad Rzeszutek Wilk To: Jan Beulich Cc: David Vrabel , Santosh.Jodh@citrix.com, Bjorn Helgaas , xhejtman@ics.muni.cz, xen-devel , boris.ostrovsky@oracle.com, mukesh.rathor@oracle.com, yuval.shaia@oracle.com, "linux-kernel@vger.kernel.org" Subject: Re: [v1 1/2] xen/p2m: Create identity mappings for PFNs beyound E820 and PCI BARs Message-ID: <20131029151129.GA20984@phenom.dumpdata.com> References: <1382713401-4882-1-git-send-email-konrad.wilk@oracle.com> <1382713401-4882-2-git-send-email-konrad.wilk@oracle.com> <20131028165837.GH4353@phenom.dumpdata.com> <526F7E9202000078000FD7A6@nat28.tlf.novell.com> <20131029144559.GI20487@phenom.dumpdata.com> <526FDA6102000078000FDAE2@nat28.tlf.novell.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <526FDA6102000078000FDAE2@nat28.tlf.novell.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Source-IP: acsinet21.oracle.com [141.146.126.237] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1549 Lines: 33 On Tue, Oct 29, 2013 at 02:55:13PM +0000, Jan Beulich wrote: > >>> On 29.10.13 at 15:45, Konrad Rzeszutek Wilk wrote: > > On Tue, Oct 29, 2013 at 08:23:30AM +0000, Jan Beulich wrote: > >> >>> On 28.10.13 at 17:58, Konrad Rzeszutek Wilk wrote: > >> > On Fri, Oct 25, 2013 at 04:08:19PM -0600, Bjorn Helgaas wrote: > >> >> If you can look at PCI host bridge apertures instead of BARs, that > >> >> would solve both problems. Reassigning those apertures is > >> >> theoretically possible but is not even a gleam in our eyes yet. > >> > > >> > I think I have to have both (BARs and host bridge apertures) as when > >> > we do PCI passthrough to a guest - we might do it without a bridge. > >> > >> Why? Aren't the host bridge ranges necessarily a superset of the > >> individual devices' BARs? > > > > Yes. But when you pass in a PCI device to a PV guest you don't pass in the > > bridge. Just the PCI device itself. > > Right you are. Which means that basing the whole logic on the > PCI device BARs is likely wrong anyway, not just because it > doesn't account for other MMIO ranges. Right, but that is OK. When you pass in a PCI device to a PV guest you only care about that specific device driver being able to access its BARs. > > Jan > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/