From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org
Cc: kirill.shutemov@linux.intel.com
Subject: Re: [Xen-devel] [PATCH] xen: support 52 bit physical addresses in pv guests
Date: Thu, 21 Sep 2017 17:16:36 +0100 [thread overview]
Message-ID: <7fa7aa6d-6458-0d86-83a4-b3b6daebfa80@citrix.com> (raw)
In-Reply-To: <b10b9dfe-7db8-fc5f-58f6-cc8c36e521c4@oracle.com>
On 21/09/17 17:00, Boris Ostrovsky wrote:
>
>>
>>>
>>>>
>>>> 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))
>>
>> Hmm, really? Shouldn't we rather add something like
>>
>> BUG_ON(sme_active());
>>
>> somewhere?
>
> We can do that too.
Please don't do anything to cause Linux to crash if Xen is using SME
itself, but leaving all of the PV guest unencrypted.
~Andrew
next prev parent reply other threads:[~2017-09-21 16:16 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
2017-09-21 14:41 ` Juergen Gross
2017-09-21 16:00 ` Boris Ostrovsky
2017-09-21 16:16 ` Andrew Cooper [this message]
2017-09-21 19:01 ` [Xen-devel] " 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=7fa7aa6d-6458-0d86-83a4-b3b6daebfa80@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=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®