[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJhGHyBdQ4nz5zg3RS11QfUKY=gUJx8G5nuYKOfzuycrDeQ3Tw@mail.gmail.com>
Date: Mon, 7 Mar 2022 22:53:53 +0800
From: Lai Jiangshan <jiangshanlai@...il.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: LKML <linux-kernel@...r.kernel.org>, X86 ML <x86@...nel.org>,
Lai Jiangshan <jiangshan.ljs@...group.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>
Subject: Re: [PATCH V2 3/7] x86/entry: move PUSH_AND_CLEAR_REGS out of error_entry
On Thu, Mar 3, 2022 at 4:55 PM Peter Zijlstra <peterz@...radead.org> wrote:
>
> And also, IIUC, folding that int80 thing a few patches down, right?
I don't think folding that int80 thing into idtentry requires this patch.
I didn't notice int80 is a huge ASM code in a different file until I finished
converting the entry code to C code. So folding int80 thing is a patch later.
It is possible to move this patch of folding int80 thing as the first patch,
but several patches need to be updated respectively. But I'm afraid of
updating ASM code without good reason which requires several days of
debugging even if there is a slight mistake, for example, forgetting to
update the offset of the stack or register name when switching two lines
of code.
Powered by blists - more mailing lists