xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Juergen Gross <jgross@suse.com>,
	ian.campbell@citrix.com, ian.jackson@eu.citrix.com,
	jbeulich@suse.com, keir@xen.org, tim@xen.org,
	xen-devel@lists.xen.org
Subject: Re: [PATCH] expand x86 arch_shared_info to support >3 level p2m tree
Date: Mon, 8 Sep 2014 14:59:59 +0100	[thread overview]
Message-ID: <540DB65F.30601@citrix.com> (raw)
In-Reply-To: <1410184138-11277-2-git-send-email-jgross@suse.com>

On 08/09/14 14:48, 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. With three levels of the p2m tree
> it is possible to support up to 512 GB of RAM for a pv domain.

Specifically only 64bit PV domains have the 512GB limit.

32bit PV domains have a far larger supported RAM as they can fit twice
as many mfns in each p2m page.

>  To be
> able to support more RAM an additional level is to be added.
>
> This patch expands struct arch_shared_info with a new p2m tree root
> and the number of levels of the p2m tree. The new information is
> indicated by the domain to be valid by storing ~0UL into
> pfn_to_mfn_frame_list_list (this should be done only if more than
> three levels are needed, of course).
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
>  xen/include/public/arch-x86/xen.h | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/xen/include/public/arch-x86/xen.h b/xen/include/public/arch-x86/xen.h
> index f35804b..b7fa2b6 100644
> --- a/xen/include/public/arch-x86/xen.h
> +++ b/xen/include/public/arch-x86/xen.h
> @@ -224,7 +224,13 @@ struct arch_shared_info {
>      /* Frame containing list of mfns containing list of mfns containing p2m. */
>      xen_pfn_t     pfn_to_mfn_frame_list_list;
>      unsigned long nmi_reason;
> -    uint64_t pad[32];
> +    /*
> +     * Following two fields are valid if pfn_to_mfn_frame_list_list contains
> +     * ~0UL.
> +     */
> +    unsigned long p2m_levels;   /* number of levels of p2m tree */
> +    xen_pfn_t     p2m_root;     /* p2m tree top level mfn */
> +    uint64_t pad[30];

This padding is now wrong, as unsigned long is only 4 bytes in 32bit,
and it is adjacent to another unsigned long.

~Andrew

>  };
>  typedef struct arch_shared_info arch_shared_info_t;
>  

  reply	other threads:[~2014-09-08 13:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 13:48 [PATCH 0/1] support >3 level p2m tree Juergen Gross
2014-09-08 13:48 ` [PATCH] expand x86 arch_shared_info to " Juergen Gross
2014-09-08 13:59   ` Andrew Cooper [this message]
2014-09-08 16:11     ` Juergen Gross
2014-09-09  9:28       ` Jan Beulich
2014-09-09  9:36         ` Andrew Cooper
2014-09-09  9:45           ` Juergen Gross
2014-09-09  9:55           ` Jan Beulich

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=540DB65F.30601@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=keir@xen.org \
    --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).