From: Keir Fraser <keir.xen@gmail.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>,
Jan Beulich <JBeulich@novell.com>
Cc: Tim Deegan <Tim.Deegan@eu.citrix.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: Mon, 14 Mar 2011 16:54:27 +0000 [thread overview]
Message-ID: <C9A3F8C3.14C45%keir.xen@gmail.com> (raw)
In-Reply-To: <1300120438.17339.2202.camel@zakaz.uk.xensource.com>
On 14/03/2011 16:33, "Ian Campbell" <Ian.Campbell@eu.citrix.com> 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
next prev parent reply other threads:[~2011-03-14 16:54 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 [this message]
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
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=C9A3F8C3.14C45%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=JBeulich@novell.com \
--cc=Tim.Deegan@eu.citrix.com \
--cc=gianni.tedesco@citrix.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).