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]: Allow tools to map arbitrarily large machp

To: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH]: Allow tools to map arbitrarily large machphys_mfn_list on 32bit dom0
From: Keir Fraser <keir.xen@xxxxxxxxx>
Date: Mon, 14 Mar 2011 16:54:27 +0000
Cc: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Gianni Tedesco <gianni.tedesco@xxxxxxxxxx>
Delivery-date: Mon, 14 Mar 2011 10:07:00 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:user-agent:date:subject:from:to:cc:message-id :thread-topic:thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=+l4+3Fjo2SKFbHAzRaTIZ8pB8MlJW9awM7IgsJsKuqE=; b=KwN8czsb6gwwaLNKjM5wjE+GyqQ8fbrR6IgWCZL1nS46go6cL8YwwDlfTwxe5WqLfK VE1PnA0aCl0FZd3Yvc4NqTGrWYzIj/46uGeMsaS46xER5CtkOVbfuHJcEAjqSmRlNUEv JxrtlCsq3+6H1XuwtHxdTkzbdVooS/yLuvyXU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=aq2JZTbaFr85lWiAQslKPW0Ma+Vj7LHBpwBf8zzM40a0zNZIxxw8OvLUpS7FZ5Omu2 OW17wKbQIIZkM+5ev7kHoOg5vq/FI0l1mx6EAcYKil2MOHbiIQj4+cK/cyzUjiGzsDij HBBiKCaJjNMQy/jmFhK+UV6xpOWKzaPpFC0S4=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1300120438.17339.2202.camel@xxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcviaHqB2U9h9rTQr0yIhOv537lbgA==
Thread-topic: [Xen-devel] Re: [PATCH]: Allow tools to map arbitrarily large machphys_mfn_list on 32bit dom0
User-agent: Microsoft-Entourage/12.28.0.101117
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?

 -- Keir



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

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