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/
Home Products Support Community News


Re: [Xen-devel] Re: [PATCH]: Allow tools to map arbitrarily large mach

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH]: Allow tools to map arbitrarily large machphys_mfn_list on 32bit dom0
From: Gianni Tedesco <gianni.tedesco@xxxxxxxxxx>
Date: Mon, 14 Mar 2011 17:09:51 +0000
Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>, Keir Fraser <keir.xen@xxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 14 Mar 2011 10:15:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D7E57A6020000780003662B@xxxxxxxxxxxxxxxxxx>
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>
References: <1300120438.17339.2202.camel@xxxxxxxxxxxxxxxxxxxxxx> <C9A3F8C3.14C45%keir.xen@xxxxxxxxx> <4D7E57A6020000780003662B@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2011-03-14 at 17:00 +0000, Jan Beulich wrote:
> >>> On 14.03.11 at 17:54, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
> > On 14/03/2011 16:33, "Ian Campbell" <Ian.Campbell@xxxxxxxxxxxxx> wrote:
> > 
> >>> But RDWR_COMPAT_MPT_VIRT_END still doesn't necessarily
> >>> cover all of the memory the machine may have (after all the
> >>> range is way smaller than RDWR_MPT_VIRT_{START,END}.
> >> 
> >> It's 1GB which is enough to cover 1TB of host memory, which AFAIK is all
> >> we support these days. It certainly buys us time compared with currently
> >> failing at 160GB.
> >> 
> >>> If that's the goal, then the patch as presented isn't suitable,
> >>> as there's not event a compat table set up for all of the
> >>> memory.
> >> 
> >> paging_init seems to do the right thing and setup the compat M2P up to a
> >> maximum of RDWR_COMPAT_MPT_VIRT_END.
> >> 
> >>>  I'd say the tools then need to have access to the
> >>> native table, reading 64-bit MFNs from it (since, with MFN
> >>> compression, we can exceed 32-bits).
> >> 
> >> That's another option I guess.
> > 
> > It's not really an option for 4.1.0. Can we at least agree that this is an
> > improvement for now, and in time for 4.1.0?
> Yes, as long as the tools can handle the extended output.

It certainly seems to work for the domain suspend case, I'm not sure
where else it might fail but it-seems-to-me(tm) that tools should be
able to handle the output that they asked for.


Xen-devel mailing list

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