From: "Jan Beulich" <JBeulich@novell.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: Tim Deegan <Tim.Deegan@eu.citrix.com>,
Keir Fraser <keir.fraser@xen.org>,
Keir Fraser <keir.xen@gmail.com>,
Xen Devel <xen-devel@lists.xensource.com>,
Gianni Tedesco <gianni.tedesco@citrix.com>
Subject: Re: Re: [PATCH]: Allow tools to map arbitrarily large machphys_mfn_list on 32bit dom0
Date: Tue, 15 Mar 2011 15:09:44 +0000 [thread overview]
Message-ID: <4D7F8F4802000078000369B9@vpn.id2.novell.com> (raw)
In-Reply-To: <1300201234.17339.2248.camel@zakaz.uk.xensource.com>
>>> On 15.03.11 at 16:00, Ian Campbell <Ian.Campbell@eu.citrix.com> wrote:
> On Mon, 2011-03-14 at 16:58 +0000, Jan Beulich wrote:
>> >>> On 14.03.11 at 17:33, Ian Campbell <Ian.Campbell@eu.citrix.com> 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.
Jan
next prev parent reply other threads:[~2011-03-15 15:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 18:52 xc: error: xc_machphys_mfn_list: 83 != 129 when suspending 32GB PV DomU Gianni Tedesco
2011-03-11 19:21 ` Keir Fraser
2011-03-14 10:20 ` Ian Campbell
2011-03-14 15:05 ` [PATCH]: Allow tools to map arbitrarily large machphys_mfn_list on 32bit dom0 Gianni Tedesco
2011-03-14 15:08 ` Keir Fraser
2011-03-14 15:11 ` Ian Campbell
2011-03-14 15:19 ` Gianni Tedesco
2011-03-14 15:55 ` Jan Beulich
2011-03-14 16:03 ` Ian Campbell
2011-03-14 16:22 ` Jan Beulich
2011-03-14 16:33 ` Ian Campbell
2011-03-14 16:54 ` Keir Fraser
2011-03-14 17:00 ` Jan Beulich
2011-03-14 17:09 ` Gianni Tedesco
2011-03-14 16:58 ` Jan Beulich
2011-03-14 17:11 ` Gianni Tedesco
2011-03-15 15:00 ` Ian Campbell
2011-03-15 15:09 ` Jan Beulich [this message]
2011-03-15 15:14 ` Ian Campbell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D7F8F4802000078000369B9@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=Tim.Deegan@eu.citrix.com \
--cc=gianni.tedesco@citrix.com \
--cc=keir.fraser@xen.org \
--cc=keir.xen@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).