From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: kirill.shutemov@linux.intel.com
Subject: Re: [PATCH] xen: support 52 bit physical addresses in pv guests
Date: Thu, 21 Sep 2017 10:14:44 -0400 [thread overview]
Message-ID: <287fb059-910e-4dc9-b21d-581c97a06323@oracle.com> (raw)
In-Reply-To: <20170921080138.22917-1-jgross@suse.com>
On 09/21/2017 04:01 AM, Juergen Gross wrote:
> Physical addresses on processors supporting 5 level paging can be up to
> 52 bits wide. For a Xen pv guest running on such a machine those
> physical addresses have to be supported in order to be able to use any
> memory on the machine even if the guest itself does not support 5 level
> paging.
>
> So when reading/writing a MFN from/to a pte don't use the kernel's
> PTE_PFN_MASK but a new XEN_PTE_MFN_MASK allowing full 40 bit wide MFNs.
full 52 bits?
>
> Signed-off-by: Juergen Gross <jgross@suse.com>
> ---
> arch/x86/include/asm/xen/page.h | 11 ++++++++++-
> arch/x86/xen/mmu_pv.c | 4 ++--
> 2 files changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/arch/x86/include/asm/xen/page.h b/arch/x86/include/asm/xen/page.h
> index 07b6531813c4..bcb8b193c8d1 100644
> --- a/arch/x86/include/asm/xen/page.h
> +++ b/arch/x86/include/asm/xen/page.h
> @@ -26,6 +26,15 @@ typedef struct xpaddr {
> phys_addr_t paddr;
> } xpaddr_t;
>
> +#ifdef CONFIG_X86_64
> +#define XEN_PHYSICAL_MASK ((1UL << 52) - 1)
SME is not supported for PV guests but for consistency (and in case sme
bit somehow gets set)
#define XEN_PHYSICAL_MASK __sme_clr(((1UL << 52) - 1))
But the real question that I have is whether this patch is sufficient.
We are trying to preserve more bits in mfn but then this mfn is used,
say, in pte_pfn_to_mfn() to build a pte. Can we be sure that the pte
won't be stripped of higher bits in native code (again, as an example,
native_make_pte()) because we are compiled with 5LEVEL?
-boris
> +#else
> +#define XEN_PHYSICAL_MASK __PHYSICAL_MASK
> +#endif
> +
> +#define XEN_PTE_MFN_MASK ((pteval_t)(((signed long)PAGE_MASK) & \
> + XEN_PHYSICAL_MASK))
> +
> #define XMADDR(x) ((xmaddr_t) { .maddr = (x) })
> #define XPADDR(x) ((xpaddr_t) { .paddr = (x) })
>
> @@ -277,7 +286,7 @@ static inline unsigned long bfn_to_local_pfn(unsigned long mfn)
>
> static inline unsigned long pte_mfn(pte_t pte)
> {
> - return (pte.pte & PTE_PFN_MASK) >> PAGE_SHIFT;
> + return (pte.pte & XEN_PTE_MFN_MASK) >> PAGE_SHIFT;
> }
>
> static inline pte_t mfn_pte(unsigned long page_nr, pgprot_t pgprot)
> diff --git a/arch/x86/xen/mmu_pv.c b/arch/x86/xen/mmu_pv.c
> index 509f560bd0c6..958d36d776d9 100644
> --- a/arch/x86/xen/mmu_pv.c
> +++ b/arch/x86/xen/mmu_pv.c
> @@ -315,7 +315,7 @@ void xen_ptep_modify_prot_commit(struct mm_struct *mm, unsigned long addr,
> static pteval_t pte_mfn_to_pfn(pteval_t val)
> {
> if (val & _PAGE_PRESENT) {
> - unsigned long mfn = (val & PTE_PFN_MASK) >> PAGE_SHIFT;
> + unsigned long mfn = (val & XEN_PTE_MFN_MASK) >> PAGE_SHIFT;
> unsigned long pfn = mfn_to_pfn(mfn);
>
> pteval_t flags = val & PTE_FLAGS_MASK;
> @@ -1740,7 +1740,7 @@ static unsigned long __init m2p(phys_addr_t maddr)
> {
> phys_addr_t paddr;
>
> - maddr &= PTE_PFN_MASK;
> + maddr &= XEN_PTE_MFN_MASK;
> paddr = mfn_to_pfn(maddr >> PAGE_SHIFT) << PAGE_SHIFT;
>
> return paddr;
>
next prev parent reply other threads:[~2017-09-21 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 8:01 Juergen Gross
2017-09-21 14:14 ` Boris Ostrovsky [this message]
2017-09-21 14:41 ` Juergen Gross
2017-09-21 16:00 ` Boris Ostrovsky
2017-09-21 16:16 ` [Xen-devel] " Andrew Cooper
2017-09-21 19:01 ` Boris Ostrovsky
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=287fb059-910e-4dc9-b21d-581c97a06323@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®