[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJhGHyDEHLvZToLPUcykWWQG4BMkR2ttytBLFOBit8_16jGM4w@mail.gmail.com>
Date: Thu, 18 Nov 2021 19:04:40 +0800
From: Lai Jiangshan <jiangshanlai@...il.com>
To: Liam Merwick <liam.merwick@...cle.com>
Cc: LKML <linux-kernel@...r.kernel.org>, X86 ML <x86@...nel.org>,
Lai Jiangshan <laijs@...ux.alibaba.com>,
Andy Lutomirski <luto@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>, Juergen Gross <jgross@...e.com>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Joerg Roedel <jroedel@...e.de>,
Javier Martinez Canillas <javierm@...hat.com>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Brijesh Singh <brijesh.singh@....com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Tom Lendacky <thomas.lendacky@....com>
Subject: Re: [PATCH V5 46/50] x86/sev: Use C entry code
On Thu, Nov 18, 2021 at 5:31 PM Liam Merwick <liam.merwick@...cle.com> wrote:
>
> On 10/11/2021 11:57, Lai Jiangshan wrote:
> > From: Lai Jiangshan <laijs@...ux.alibaba.com>
> >
> > Use DEFINE_IDTENTRY_IST_ETNRY_ERRORCODE to emit C entry function and
> > use the function directly in entry_64.S.
> >
>
> A drive-by comment as I was looking for SEV commits...
>
> Typo in definition names, ETNRY -> ENTRY, (which impacts most patches
> between 38-48) would likely cause confusion in the future.
>
Wow, what a study mistake.
Thanks
Lai
Powered by blists - more mailing lists