From: Keir Fraser <keir.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>, Tim Deegan <tim@xen.org>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH] x86/mm: remove the linear mapping of the p2m tables
Date: Thu, 13 Sep 2012 16:17:18 +0100 [thread overview]
Message-ID: <CC77B78E.3EAFE%keir.xen@gmail.com> (raw)
In-Reply-To: <50521304020000780009B208@nat28.tlf.novell.com>
On 13/09/2012 16:08, "Jan Beulich" <JBeulich@suse.com> wrote:
>>>> On 13.09.12 at 16:58, Keir Fraser <keir.xen@gmail.com> wrote:
>> On 13/09/2012 15:42, "Tim Deegan" <tim@xen.org> wrote:
>>
>>>> Is that also going to remain true when we won't be able to 1:1-
>>>> map all of the memory anymore once we break the current 5Tb
>>>> barrier? If not, it would probably be worthwhile keeping that
>>>> code.
>>>
>>> Ah, 5TB is a smaller limit than I thought we had. Yes, better leave it
>>> alone, so. Though TBH finding some way to use a bit more virtual
>>> address space for Xen seems like a good idea anyway, since this won't be
>>> the only place we'll want to avoid TLB flushes.
>>
>> For HVM or PVH guests, where this HAP code would be used, clearly Xen can
>> use all the virtual address space it wants. It will almost certainly make
>> sense for Xen to have a 1:1 physical mapping of all memory when running such
>> a guest, and only do mapcache type tricks when running legacy PV guests.
>
> Yes, that's the mode I indeed wanted to get to. Just that it's
> not really clear to me (without having started at least the
> work of bumping the boundary) how intrusive those changes
> are going to be.
Well, this is true. But almost regardless of the complexity, this is how
we're going to want to do it, and it does mean we won't need the linear map.
:)
-- Keir
> Jan
>
next prev parent reply other threads:[~2012-09-13 15:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 14:01 [PATCH] x86/mm: remove the linear mapping of the p2m tables Tim Deegan
2012-09-13 14:23 ` Jan Beulich
2012-09-13 14:42 ` Tim Deegan
2012-09-13 14:58 ` Keir Fraser
2012-09-13 15:08 ` Jan Beulich
2012-09-13 15:17 ` Keir Fraser [this message]
2012-09-13 15:36 ` Jan Beulich
2012-09-13 15:11 ` Tim Deegan
2012-09-13 15:18 ` Keir Fraser
2012-09-13 20:43 ` Konrad Rzeszutek Wilk
2012-09-13 21:14 ` Keir Fraser
2012-09-14 20:31 ` Konrad Rzeszutek Wilk
2012-09-14 20:55 ` Keir Fraser
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=CC77B78E.3EAFE%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=JBeulich@suse.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
/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).