[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <E940A2E7-6FAC-4E87-96DE-596BA3F505AF@infradead.org>
Date: Sat, 25 Feb 2023 12:55:12 +0000
From: David Woodhouse <dwmw2@...radead.org>
To: Brian Gerst <brgerst@...il.com>
CC: Usama Arif <usama.arif@...edance.com>,
linux-kernel@...r.kernel.org, x86@...nel.org,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>,
"H . Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Andy Lutomirski <luto@...nel.org>,
Ingo Molnar <mingo@...nel.org>
Subject: Re: [External] [PATCH v2 0/5] x86-64: Remove global variables from boot
On 25 February 2023 12:47:33 GMT, Brian Gerst <brgerst@...il.com> wrote:
>On Sat, Feb 25, 2023 at 5:20 AM David Woodhouse <dwmw2@...radead.org> wrote:
>>
>> On Fri, 2023-02-24 at 16:38 -0500, Brian Gerst wrote:
>> > Removing the globals before the parallel boot series, would be the
>> > best option IMO. That would make the transition simpler.
>>
>> Looks like this:
>>
>> https://git.infradead.org/users/dwmw2/linux.git/shortlog/refs/heads/parallel-6.2-rc8-brfirst
>>
>> Passes basic smoke testing in qemu, including suspend to RAM and
>> offlining CPU0.
>
>Looks good, thanks.
Aside from the fact that I forgot to put the tr_lock into the other startup paths that load the realmode %esp. But I'll let Usama do that now.
I can probably work out how to test the AMD SEV path; is there a way I can test the startup_64 MADT one?
Powered by blists - more mailing lists