[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240103212616.GGZZXQ+IKGPb+EqVcu@fat_crate.local>
Date: Wed, 3 Jan 2024 22:26:16 +0100
From: Borislav Petkov <bp@...en8.de>
To: Nathan Chancellor <nathan@...nel.org>
Cc: tglx@...utronix.de, mingo@...hat.com, dave.hansen@...ux.intel.com,
x86@...nel.org, mhiramat@...nel.org, linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev, patches@...ts.linux.dev
Subject: Re: [PATCH] x86/tools: objdump_reformat.awk: Skip bad instructions
from llvm-objdump
On Wed, Jan 03, 2024 at 01:55:06PM -0700, Nathan Chancellor wrote:
> On Wed, Jan 03, 2024 at 07:18:52PM +0100, Borislav Petkov wrote:
> > On Wed, Jan 03, 2024 at 11:15:42AM -0700, Nathan Chancellor wrote:
> > > Ping? I am still seeing this issue.
> >
> > Does this need a Fixes tag and needs to go to Linus now or are you fine
> > with 6.8-rc0?
>
> This is only needed due to the recent changes from Sam and myself in
> x86/build
I don't understand: those three commits seem unrelated to LLVM objdump
outputting "<unknown>".
Or are you saying that you've *started* running the insn decoder selftest
with llvm's objdump and those three commits are addressing differences
in the output and this outstanding commit is needed too for the bad
opcode case?
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists