All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juergen Gross <jgross@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel@lists.xensource.com, jbeulich@suse.com,
	konrad.wilk@oracle.com, david.vrabel@citrix.com
Subject: Re: [PATCH 1/4] expand x86 arch_shared_info to support linear p2m list
Date: Fri, 14 Nov 2014 13:53:08 +0100	[thread overview]
Message-ID: <5465FB34.9010606@suse.com> (raw)
In-Reply-To: <5465EA63.3010007@citrix.com>

On 11/14/2014 12:41 PM, Andrew Cooper wrote:
> On 14/11/14 09:37, Juergen Gross wrote:
>> The x86 struct arch_shared_info field pfn_to_mfn_frame_list_list
>> currently contains the mfn of the top level page frame of the 3 level
>> p2m tree, which is used by the Xen tools during saving and restoring
>> (and live migration) of pv domains and for crash dump analysis. With
>> three levels of the p2m tree it is possible to support up to 512 GB of
>> RAM for a 64 bit pv domain.
>>
>> A 32 bit pv domain can support more, as each memory page can hold 1024
>> instead of 512 entries, leading to a limit of 4 TB.
>>
>> To be able to support more RAM on x86-64 switch to a virtual mapped
>> p2m list.
>>
>> This patch expands struct arch_shared_info with a new p2m list virtual
>> address and the mfn of the page table root. The new information is
>> indicated by the domain to be valid by storing ~0UL into
>> pfn_to_mfn_frame_list_list. The hypervisor indicates usability of this
>> feature by a new flag XENFEAT_virtual_p2m.
>
> How do you envisage this being used?  Are you expecting the tools to do
> manual pagetable walks using xc_map_foreign_xxx() ?

Yes. Not very different compared to today's mapping via the 3 level
p2m tree. Just another entry format, 4 instead of 3 levels and starting
at an offset.


Juergen

  reply	other threads:[~2014-11-14 12:53 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14  9:37 [PATCH 0/4] support guest virtual mapped p2m list Juergen Gross
2014-11-14  9:37 ` [PATCH 1/4] expand x86 arch_shared_info to support linear " Juergen Gross
2014-11-14 11:41   ` Andrew Cooper
2014-11-14 12:53     ` Juergen Gross [this message]
2014-11-14 13:56       ` Andrew Cooper
2014-11-14 14:14         ` Jürgen Groß
2014-11-14 14:59           ` Andrew Cooper
2014-11-14 15:32             ` Juergen Gross
2014-11-14 16:08               ` Andrew Cooper
2014-11-18  5:33                 ` Juergen Gross
2014-11-18 10:51                   ` Andrew Cooper
2014-11-18 10:56                     ` David Vrabel
2014-11-21 12:23   ` Jan Beulich
2014-11-21 12:57     ` Juergen Gross
2014-11-21 13:26       ` Andrew Cooper
2014-11-21 13:37         ` Jürgen Groß
2014-11-21 14:04           ` Andrew Cooper
2014-11-21 14:07           ` Jan Beulich
2014-11-14  9:37 ` [PATCH 2/4] introduce arch_get_features() Juergen Gross
2014-11-21 12:26   ` Jan Beulich
2014-11-21 13:21   ` Julien Grall
2014-11-14  9:37 ` [PATCH 3/4] introduce boot parameter for setting XENFEAT_virtual_p2m Juergen Gross
2014-11-19 21:04   ` Konrad Rzeszutek Wilk
2014-11-20  4:46     ` Juergen Gross
2014-11-14  9:37 ` [PATCH 4/4] document new boot parameter virt_p2m 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=5465FB34.9010606@suse.com \
    --to=jgross@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=david.vrabel@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=konrad.wilk@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.