From: Brijesh Singh <brijesh.singh@amd.com>
To: Borislav Petkov <bp@alien8.de>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>
Cc: brijesh.singh@amd.com,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
X86 ML <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: SME/32-bit regression
Date: Wed, 6 Sep 2017 13:06:50 -0500 [thread overview]
Message-ID: <56f022a2-e363-0524-68ba-c31950d96e0d@amd.com> (raw)
In-Reply-To: <20170906164417.2terp5ioelzglehq@pd.tnic>
On 09/06/2017 11:44 AM, Borislav Petkov wrote:
> On Wed, Sep 06, 2017 at 04:30:23PM +0000, Lendacky, Thomas wrote:
>> Sorry for the top post, I'm on holiday and don't have access to a good
>> email client... I went with unsigned long to match all the page table
>> related declarations. If changing to u64 doesn't generate any warnings
>> or other issues them I'm good with that.
>
> Ok, no worries. Lemme run the smoke-tests on it and test it to see
> everything else still works.
>
I did the following quick run with your patch and everything seems to be
working okay
64-bit build:
-------
1) Baremetal SME *enabled* - System boots fine
a) 32-bit guest launch : successful (KVM HV)
b) 64-bit guest launch : successful (KVM HV)
c) 64-bit SEV guest launch : successful (KVM HV)
2) Baremetal SME *disabled* - System boots fine
a) 32-bit guest launch : successful (KVM HV)
b) 64-bit guest launch : successful (KVM HV)
c) 64-bit SEV guest launch : successful (KVM HV)
32-bit build
----------
I am installing 32-bit distro to verify 32-bit baremetal boot and will
report my findings soon.
-Brijesh
next prev parent reply other threads:[~2017-09-06 18:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 3:45 Boris Ostrovsky
2017-09-06 9:26 ` Borislav Petkov
2017-09-06 9:45 ` Borislav Petkov
[not found] ` <CY4PR12MB11415936E980489690575E65EC970@CY4PR12MB1141.namprd12.prod.outlook.com>
2017-09-06 16:44 ` Borislav Petkov
2017-09-06 18:06 ` Brijesh Singh [this message]
2017-09-06 18:19 ` Borislav Petkov
2017-09-06 21:03 ` Boris Ostrovsky
2017-09-07 0:26 ` Brijesh Singh
2017-09-07 9:38 ` [PATCH] x86/mm: Make the SME mask a u64 Borislav Petkov
2017-09-07 10:34 ` [tip:x86/urgent] " tip-bot for Borislav Petkov
2017-09-06 13:54 ` SME/32-bit regression Boris Ostrovsky
2017-09-06 13:57 ` Thomas Gleixner
2017-09-06 14:03 ` 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=56f022a2-e363-0524-68ba-c31950d96e0d@amd.com \
--to=brijesh.singh@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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®