[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yh3cPSf/qKNPv1C9@nazgul.tnic>
Date: Tue, 1 Mar 2022 09:41:50 +0100
From: Borislav Petkov <bp@...en8.de>
To: Ammar Faizi <ammarfaizi2@...weeb.org>
Cc: weidonghui <weidonghui@...winnertech.com>, tools@...ux.kernel.org,
linux-kernel@...r.kernel.org, gwml@...r.gnuweeb.org,
x86@...nel.org, Andrew Morton <akpm@...ux-foundation.org>,
Andy Lutomirski <luto@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] scripts/decodecode: Make objdump always use operand-size
suffix
On Tue, Mar 01, 2022 at 11:11:19AM +0700, Ammar Faizi wrote:
> For better reading, always use operand-size suffix for the generated
What does "better reading" mean here exactly?
See, there's a reason why -M suffix is not default in objdump. And in
my experience, I've never looked at objdump output and thought, "hm, so
the operand size insn mnemonic suffix is missing here". And if at all,
one usually wants to know the operand size of a single instruction - not
the whole bunch - and for that we tend to look at the vendor manuals
directly...
So I don't think this brings any improvement to the output but hey, I
could be missing a reason.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists