WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [PATCH 0 of 3] Patches for PCI passthrough with modi

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH 0 of 3] Patches for PCI passthrough with modified E820 (v3) - resent.
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Tue, 10 May 2011 16:09:58 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Tue, 10 May 2011 08:10:40 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110510145322.GA17128@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Organization: Citrix Systems, Inc.
References: <patchbomb.1304518670@xxxxxxxxxxxxxxxxxxxxxxx> <1304931630.26692.205.camel@xxxxxxxxxxxxxxxxxxxxxx> <20110509210140.GA29498@xxxxxxxxxxxx> <1305016202.26692.255.camel@xxxxxxxxxxxxxxxxxxxxxx> <20110510145322.GA17128@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2011-05-10 at 15:53 +0100, Konrad Rzeszutek Wilk wrote:
>  
> > > > > This has been tested with 2.6.18 (RHEL5), 2.6.27(SLES11), 2.6.36, 
> > > > > 2.6.37, 2.6.38,
> > > > > and 2.6.39 kernels. Also tested with PV NetBSD 5.1.
> > 
> > They all saw the full amount of RAM? Since the domain builder does not
> 
> Correct. So if the guest had 6GB passed in, roughly 3GB ended below the
> 4GB mark, and then rest - 3GB got stuck behind the 4GB.

Do you happen to know what caused that to work? I wasn't aware of any
code which moved the p2m around based on e820 in older guests (and I
can't find any right now) and I didn't think the builder itself paid any
attention to the e820 either.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>