From: Thorsten Glaser <tg@debian.org>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
x86@kernel.org, rostedt@goodmis.org,
linux-kernel@vger.kernel.org, linux-toolchains@vger.kernel.org,
jpoimboe@redhat.com, alexei.starovoitov@gmail.com,
mhiramat@kernel.org
Subject: Re: [PATCH 1/2] x86: Remove dynamic NOP selection
Date: Sat, 20 Jan 2024 17:19:16 +0000 (UTC) [thread overview]
Message-ID: <Pine.BSM.4.64L.2401201711130.29203@herc.mirbsd.org> (raw)
In-Reply-To: <CAHk-=whtFk2DoO8WhtmsbU9nGXUd8sKShV1Dk71krFLBjPUSeg@mail.gmail.com>
Linus Torvalds dixit:
>On that note, does anybody have a better disassembler than objdump? Or
>even a script around it to make it more useful? I do use "objdump
>--disassemble" a fair amount, and I hate how bad it is.
Other than -Mintel (and -Mintel,i8086 for boot code) to make the
syntax 90–95% less awful, I’m sorry I’ve also been looking.
>My pet peeve is the crazy relocation handling (or lack there-of). IOW,
Yes! This!
I’ve been putting markers into the file and then disassembling
the final linked thing instead of just the object file I need
because of this.
>Is there some sane tool that just does the sane thing and shows this as
The only other disassemblers I know don’t know about ELF objects
at all, I’m sorry to say.
I didn’t know about objdump -r, but that’s truly awful to read.
Given a wide enough screen, an intermediate | sed 's/^\t/&&&&/'
at least moves the relocation info more to the right to interrupt
the reading flow less.
Thanks,
//mirabilos
--
FWIW, I'm quite impressed with mksh interactively. I thought it was much
*much* more bare bones. But it turns out it beats the living hell out of
ksh93 in that respect. I'd even consider it for my daily use if I hadn't
wasted half my life on my zsh setup. :-) -- Frank Terbeck in #!/bin/mksh
next prev parent reply other threads:[~2024-01-20 17:21 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 11:32 [PATCH 0/2] x86: Remove ideal_nops[] Peter Zijlstra
2021-03-12 11:32 ` [PATCH 1/2] x86: Remove dynamic NOP selection Peter Zijlstra
2021-03-12 12:09 ` Peter Zijlstra
2021-03-12 20:36 ` Linus Torvalds
2024-01-20 6:58 ` Thorsten Glaser
2024-01-20 8:22 ` H. Peter Anvin
2024-01-20 16:53 ` Thorsten Glaser
2024-01-21 23:21 ` H. Peter Anvin
2024-01-21 23:58 ` Thorsten Glaser
2024-01-22 0:15 ` H. Peter Anvin
2024-01-22 0:56 ` Steven Rostedt
2024-01-22 1:17 ` Thorsten Glaser
2024-01-22 2:04 ` H. Peter Anvin
2024-01-22 2:15 ` H. Peter Anvin
2024-01-22 2:22 ` Steven Rostedt
2024-01-22 2:31 ` H. Peter Anvin
2024-01-20 17:00 ` Linus Torvalds
2024-01-20 17:19 ` Thorsten Glaser [this message]
2024-01-20 18:21 ` disassemblers (was Re: [PATCH 1/2] x86: Remove dynamic NOP selection) Thorsten Glaser
2024-01-21 22:36 ` [PATCH 1/2] x86: Remove dynamic NOP selection David Laight
2024-01-21 23:10 ` H. Peter Anvin
2021-03-12 11:32 ` [PATCH 2/2] objtool,x86: Use asm/nops.h Peter Zijlstra
2021-03-12 14:29 ` [PATCH 0/2] x86: Remove ideal_nops[] Sedat Dilek
2021-03-12 14:47 ` Borislav Petkov
2021-03-12 17:26 ` Steven Rostedt
2021-03-12 17:35 ` Sedat Dilek
2021-03-12 17:46 ` Borislav Petkov
2021-03-12 17:47 ` Steven Rostedt
2021-03-12 18:13 ` Sedat Dilek
2021-03-12 19:03 ` Sedat Dilek
2021-03-12 20:59 ` Borislav Petkov
[not found] ` <CA+icZUWSCS6vAQOXoG6nsW+Dbnogivzf+rmegCTMjz5hjE5cKQ@mail.gmail.com>
2021-03-13 8:49 ` Borislav Petkov
2021-03-13 11:23 ` Borislav Petkov
2021-03-13 12:10 ` Sedat Dilek
2021-03-13 12:15 ` Borislav Petkov
2021-03-13 12:38 ` Sedat Dilek
2021-03-13 12:49 ` Borislav Petkov
2021-03-13 12:58 ` Sedat Dilek
2021-03-13 13:29 ` Borislav Petkov
2021-03-13 13:47 ` Sedat Dilek
2021-03-15 17:04 ` Sedat Dilek
2021-03-15 17:15 ` Borislav Petkov
2021-03-15 17:19 ` Sedat Dilek
2021-03-15 17:23 ` Borislav Petkov
2021-03-15 18:10 ` Peter Zijlstra
2021-03-15 18:23 ` Sedat Dilek
2021-03-15 22:14 ` Peter Zijlstra
2021-03-16 5:56 ` Sedat Dilek
2021-03-27 12:08 ` Sedat Dilek
2021-03-27 20:02 ` Linus Torvalds
2021-03-30 12:31 ` Sedat Dilek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.BSM.4.64L.2401201711130.29203@herc.mirbsd.org \
--to=tg@debian.org \
--cc=alexei.starovoitov@gmail.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-toolchains@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=torvalds@linuxfoundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).