[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQXj8Rw-imK-BPDYSzR2QBu+hWFXCFzp0NV5Odz+SivZog@mail.gmail.com>
Date: Wed, 2 Mar 2016 16:13:01 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Borislav Petkov <bp@...en8.de>, Brian Gerst <brgerst@...il.com>,
X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
Tom Lendacky <thomas.lendacky@....com>
Subject: Re: [RFC PATCH] x86: Make sure verify_cpu has a good stack
On Wed, Mar 2, 2016 at 2:32 PM, H. Peter Anvin <hpa@...or.com> wrote:
>
> I'm trying to think of any reason why we couldn't simply have a symbol at the top of the initial stack? Then a simple leaq would suffice; this is for the BSP after all.
Why do we need to call verify_cpu in arch/x86/kernel/head_64.S aka the
vmlinux again ?
Is that already called in arch/x86/boot/compressed/head_64.S?
Or Tom is using 64bit bootloader that use vmlinux instead of bzImage?
Thanks
Yinghai
Powered by blists - more mailing lists