From: Miroslav Benes <mbenes@suse.cz>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: x86@kernel.org, Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Andy Lavr <andy.lavr@gmail.com>
Subject: Re: [PATCH v3 0/2] objtool: altinstructions fix and cleanup
Date: Fri, 3 Sep 2021 13:16:28 +0200 (CEST) [thread overview]
Message-ID: <alpine.LSU.2.21.2109031316200.7852@pobox.suse.cz> (raw)
In-Reply-To: <20210822225037.54620-1-joe.lawrence@redhat.com>
On Sun, 22 Aug 2021, Joe Lawrence wrote:
> This version won't eat your memory and swap when building the entire
> kernel. Apologies to Andy who discovered this over the weekend.
>
> Tested full build and boot w/o problem. The vmlinux sections, relocs,
> size, etc. all appear to be the same before and after this set.
> External tooling (kpatch-build) is happy, too.
>
> v3:
> - fix bug introduced in arch_decode_instruction() [andy]
>
> v2:
> - drop the sec->len update from the first patch [josh]
> - rip out sec->len as suggested [josh]
>
>
> Joe Lawrence (2):
> objtool: make .altinstructions section entry size consistent
> objtool: remove redundant len value from struct section
Reviewed-by: Miroslav Benes <mbenes@suse.cz>
M
next prev parent reply other threads:[~2021-09-03 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-22 22:50 Joe Lawrence
2021-08-22 22:50 ` [PATCH v3 1/2] objtool: make .altinstructions section entry size consistent Joe Lawrence
2021-10-06 22:46 ` [tip: objtool/core] objtool: Make " tip-bot2 for Joe Lawrence
2021-08-22 22:50 ` [PATCH v3 2/2] objtool: remove redundant len value from struct section Joe Lawrence
2021-10-06 22:46 ` [tip: objtool/core] objtool: Remove redundant 'len' field " tip-bot2 for Joe Lawrence
2021-09-03 11:16 ` Miroslav Benes [this message]
2021-09-04 4:46 ` [PATCH v3 0/2] objtool: altinstructions fix and cleanup Josh Poimboeuf
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=alpine.LSU.2.21.2109031316200.7852@pobox.suse.cz \
--to=mbenes@suse.cz \
--cc=andy.lavr@gmail.com \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®