From: David Vrabel <david.vrabel@citrix.com>
To: Juergen Gross <jgross@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Cc: <boris.ostrovsky@oracle.com>, <xen-devel@lists.xensource.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] [PATCH 0/2] xen: Switch to virtual mapped linear p2m list
Date: Tue, 28 Oct 2014 12:39:37 +0000 [thread overview]
Message-ID: <544F8E89.6070006@citrix.com> (raw)
In-Reply-To: <544F8713.9040803@suse.com>
On 28/10/14 12:07, Juergen Gross wrote:
>
> Okay, back to the original question: is the (up to) 64 MB virtual
> mapping of the p2m list on 32-bit pv domains a problem or not?
I think up-to 64 MiB of vmalloc area is fine. The vmalloc space can be
increased with a command line option in the unlikely event that there
are domUs that would be affected.
> If yes, the virtual mapped linear p2m list could still be used on
> 64 bit domains, paving the way for support of more than 512 GB of
> domain memory. OTOH having to keep the p2m tree coding alive isn't
> my favorite solution...
Having to keep both the tree and linear p2m code would be awful. Let's
not do this!
David
next prev parent reply other threads:[~2014-10-28 12:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 14:52 [PATCH 0/2] xen: Switch to virtual mapped linear p2m list Juergen Gross
2014-10-27 14:52 ` [PATCH 1/2] Xen: Delay remapping memory of pv-domain Juergen Gross
2014-10-28 17:34 ` David Vrabel
2014-10-29 5:30 ` Juergen Gross
2014-10-29 5:43 ` Juergen Gross
2014-10-27 14:52 ` [PATCH 2/2] Xen: switch to linear virtual mapped sparse p2m list Juergen Gross
2014-10-28 17:55 ` David Vrabel
2014-10-27 15:16 ` [PATCH 0/2] xen: Switch to virtual mapped linear " David Vrabel
2014-10-28 5:00 ` Juergen Gross
2014-10-28 9:51 ` [Xen-devel] " Ian Campbell
2014-10-28 11:53 ` Andrew Cooper
2014-10-28 12:07 ` Juergen Gross
2014-10-28 12:39 ` David Vrabel [this message]
2014-10-28 12:42 ` Andrew Cooper
2014-10-28 12:44 ` David Vrabel
2014-10-28 12:46 ` Andrew Cooper
2014-10-28 13:03 ` Juergen Gross
2014-10-28 13:04 ` Juergen Gross
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=544F8E89.6070006@citrix.com \
--to=david.vrabel@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--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