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