[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e40efa3-3d16-4fc6-8686-2bcb254c7c5e@amd.com>
Date: Mon, 4 Mar 2024 16:41:24 -0600
From: Tom Lendacky <thomas.lendacky@....com>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: Ard Biesheuvel <ardb+git@...gle.com>, linux-kernel@...r.kernel.org,
Kevin Loughlin <kevinloughlin@...gle.com>,
Dionna Glaze <dionnaglaze@...gle.com>, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, Andy Lutomirski
<luto@...nel.org>, Brian Gerst <brgerst@...il.com>
Subject: Re: [PATCH v7 0/9] x86: Confine early 1:1 mapped startup code
On 3/4/24 13:13, Ard Biesheuvel wrote:
> On Mon, 4 Mar 2024 at 18:07, Tom Lendacky <thomas.lendacky@....com> wrote:
>>
>> On 2/27/24 09:19, Ard Biesheuvel wrote:
>>> From: Ard Biesheuvel <ardb@...nel.org>
>>>
>>> This is resend #2 of v5 [0] with some touchups applied.
>>>
>>> Changes since v6:
>>> - Drop flawed patch to move some SME/SEV related calls out of the early
>>> boot path to avoid the potential need for backporting patches #6/#7
>>> to kernels where SEV support may not be crucial. This problem will be
>>> dealt with if/when it arises while doing those backports.
>>>
>>> Changes since v5:
>>> - drop patches that have been merged
>>> - rebase onto latest tip/x86/boot
>>> - fix comment regarding CR4.PGE wrt flushing of global TLB entries
>>> - avoid adding startup code to .noinstr.text as it triggers objtool
>>> warnings
>>>
>>> [0] https://lore.kernel.org/all/20240221113506.2565718-18-ardb+git@google.com/
>>>
>>> Cc: Kevin Loughlin <kevinloughlin@...gle.com>
>>> Cc: Tom Lendacky <thomas.lendacky@....com>
>>> Cc: Dionna Glaze <dionnaglaze@...gle.com>
>>> Cc: Thomas Gleixner <tglx@...utronix.de>
>>> Cc: Ingo Molnar <mingo@...hat.com>
>>> Cc: Borislav Petkov <bp@...en8.de>
>>> Cc: Dave Hansen <dave.hansen@...ux.intel.com>
>>> Cc: Andy Lutomirski <luto@...nel.org>
>>> Cc: Brian Gerst <brgerst@...il.com>
>>
>> For the series, tested bare metal boots with mem_encrypt=on /
>> mem_encrypt=off and boots of SVM, SEV, SEV-ES and SEV-SNP guests.
>>
>> Tested-by: Tom Lendacky <thomas.lendacky@....com>
>>
>
> Thanks a lot! I take it this was a kernel built with GCC?
Yes, it was a GCC build, so I went back and rebuilt with Clang-14 and
everything was fine there, too.
Thanks,
Tom
Powered by blists - more mailing lists