From: Peter Zijlstra <peterz@infradead.org>
To: jpoimboe@redhat.com
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org, mbenes@suse.cz
Subject: [PATCH 0/2] objtool: Avoid pointless modifications
Date: Thu, 07 Oct 2021 23:22:11 +0200 [thread overview]
Message-ID: <20211007212211.366874577@infradead.org> (raw)
While chasing that libelf warning, I started wondering why we're re-writing the
elf file to begin with, the second/noinstr pass shouldn't modify the image, so
we shouldn't end up in elf_write() in the first place.
These here two patches seem to cure this and should thereby also improve
performance somewhat.
next reply other threads:[~2021-10-07 21:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 21:22 Peter Zijlstra [this message]
2021-10-07 21:22 ` [PATCH 1/2] objtool: Optimize re-writing jump_label Peter Zijlstra
2021-10-08 6:55 ` Josh Poimboeuf
2021-10-08 10:03 ` Peter Zijlstra
2021-10-08 16:28 ` Josh Poimboeuf
2021-10-07 21:22 ` [PATCH 2/2] objtool: Optimize/fix retpoline alternative generation Peter Zijlstra
2021-10-08 7:23 ` Josh Poimboeuf
2021-10-08 10:35 ` Peter Zijlstra
2021-10-08 16:39 ` Josh Poimboeuf
2021-10-09 10:42 ` Peter Zijlstra
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=20211007212211.366874577@infradead.org \
--to=peterz@infradead.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbenes@suse.cz \
/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
all inboxes | Powered by JetHome®