From: Thomas Gleixner <tglx@linutronix.de>
To: Alexey Dobriyan <adobriyan@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] x86/alternative: record .altinstructions section entity size
Date: Tue, 05 Apr 2022 21:24:02 +0200 [thread overview]
Message-ID: <87o81f1gh9.ffs@tglx> (raw)
In-Reply-To: <Yi4ybwog/H4gk5Ts@localhost.localdomain>
On Sun, Mar 13 2022 at 21:05, Alexey Dobriyan wrote:
> On Sat, Mar 12, 2022 at 10:17:40PM +0100, Peter Zijlstra wrote:
>> On Fri, Mar 11, 2022 at 05:43:10PM +0300, Alexey Dobriyan wrote:
>> > + ".pushsection .altinstructions,\"aM\",@progbits," __stringify(sizeof_struct_alt_instr) "\n"\
>> > + ".pushsection .altinstructions,\"aM\",@progbits," __stringify(sizeof_struct_alt_instr) "\n"\
>> > + ".pushsection .altinstructions,\"aM\",@progbits," __stringify(sizeof_struct_alt_instr) "\n"\
>>
>> > + .pushsection .altinstructions,"aM",@progbits,sizeof_struct_alt_instr
>> > + .pushsection .altinstructions,"aM",@progbits,sizeof_struct_alt_instr
>>
>> Aside of adding entsize, you're also adding the M(ergable) bit. Also,
>> those lines are on the unwieldy side of things.
>
> binutils doc says
>
> https://sourceware.org/binutils/docs/as/Section.html
>
> If flags contains the M symbol then the type argument must be specified as well as an extra argument—entsize—like this:
>
> .section name , "flags"M, @type, entsize
>
> Sections with the M flag but not S flag must contain fixed size constants,
> each entsize octets long. Sections with both M and S must contain zero
> terminated strings where each character is entsize bytes long. The linker
> may remove duplicates within sections with the same name, same entity size
> and same flags. entsize must be an absolute expression. For sections with
> both M and S, a string which is a suffix of a larger string is considered
> a duplicate. Thus "def" will be merged with "abcdef"; A reference to the
> first "def" will be changed to a reference to "abcdef"+3.
>
> "a"M doesn't work, but "aM" does.
>
> I don't know if merging is the issue, it is not like alt replacements have names.
That does not matter. M merges any duplications in sections with the
same [section] name, entity size and flags.
.pushsection .bar "aM" @progbits, 4
.byte 0x01, 0x02, 0x03, 0x04
.popsection
.pushsection .bar "aM" @progbits, 4
.byte 0x01, 0x02, 0x03, 0x04
.popsection
Will create a section .bar with lenght 4 and the content:
0x1,0x2,0x3,0x4
What saves you here is the fact that the altinstruction entries are
guaranteed to be unique, but that wants a big fat comment.
Thanks,
tglx
next prev parent reply other threads:[~2022-04-06 0:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 14:43 [PATCH 1/5] x86/alternative: simplify DUMP_BYTES macro Alexey Dobriyan
2022-03-11 14:43 ` [PATCH 2/5] x86/alternative: bump MAX_PATCH_LEN Alexey Dobriyan
2022-03-11 14:43 ` [PATCH 3/5] x86/alternative: record .altinstructions section entity size Alexey Dobriyan
2022-03-12 21:17 ` Peter Zijlstra
2022-03-13 18:05 ` Alexey Dobriyan
2022-04-05 19:24 ` Thomas Gleixner [this message]
2022-04-06 8:30 ` Rasmus Villemoes
2022-03-11 14:43 ` [PATCH 4/5] x86/alternative: make .altinstr_replacement section non-executable Alexey Dobriyan
2022-03-12 15:31 ` Peter Zijlstra
2022-03-11 14:43 ` [PATCH 5/5] x86/unwind/orc: delete dead write in __orc_find() Alexey Dobriyan
2022-03-11 15:13 ` David Laight
2022-03-11 16:59 ` Alexey Dobriyan
2022-03-12 16:36 ` [PATCH 1/5] x86/alternative: simplify DUMP_BYTES macro Joe Perches
2022-03-13 0:14 ` Joe Perches
2022-03-13 18:09 ` Alexey Dobriyan
2022-03-14 3:21 ` Joe Perches
2022-04-03 22:25 ` Borislav Petkov
2022-04-05 16:36 ` Thomas Gleixner
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=87o81f1gh9.ffs@tglx \
--to=tglx@linutronix.de \
--cc=adobriyan@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.