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 machp

To: Jan Beulich <JBeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH]: Allow tools to map arbitrarily large machphys_mfn_list on 32bit dom0
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Tue, 15 Mar 2011 15:14:58 +0000
Cc: Tim Deegan <Tim.Deegan@xxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxx>, Keir Fraser <keir.xen@xxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Gianni Tedesco <gianni.tedesco@xxxxxxxxxx>
Delivery-date: Tue, 15 Mar 2011 08:15:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D7F8F4802000078000369B9@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>
Organization: Citrix Systems, Inc.
References: <C9A026BF.14A37%keir.xen@xxxxxxxxx> <1300098009.17339.2110.camel@xxxxxxxxxxxxxxxxxxxxxx> <1300115112.17229.78.camel@xxxxxxxxxxxxxxxxxxxxxx> <1300115469.17339.2188.camel@xxxxxxxxxxxxxxxxxxxxxx> <1300115967.17229.82.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D7E489302000078000365B5@xxxxxxxxxxxxxxxxxx> <1300118618.17339.2194.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D7E4ED302000078000365E9@xxxxxxxxxxxxxxxxxx> <1300120438.17339.2202.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D7E57460200007800036628@xxxxxxxxxxxxxxxxxx> <1300201234.17339.2248.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D7F8F4802000078000369B9@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2011-03-15 at 15:09 +0000, Jan Beulich wrote:
> >>> On 15.03.11 at 16:00, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx> wrote:
> > On Mon, 2011-03-14 at 16:58 +0000, Jan Beulich wrote:
> >> >>> On 14.03.11 at 17:33, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx> wrote:
> >> > paging_init seems to do the right thing and setup the compat M2P up to a
> >> > maximum of RDWR_COMPAT_MPT_VIRT_END.
> >> 
> >> With 1Gb being the theoretical limit of what a 32-bit guest can
> >> see and access, that's all a guest could ever sensibly ask for (a
> >> [hypothetical] domain could ask for having a larger than the
> >> default hole with more of the table mapped in).
> > 
> > The size of a domain's hypervisor hole and how much of the m2p it can
> > map via XENMEM_machphys_mfn_list have no relationship though -- that's
> > the point of this change.
> I understand that (now) - I was just trying to explain why things
> were coded to setup the full range, but expose only what would
> be visible through the hole.

Ah, right, makes sense.


Xen-devel mailing list