From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Sathvika Vasireddy <sv@linux.vnet.ibm.com>,
"npiggin@gmail.com" <npiggin@gmail.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"sv@linux.ibm.com" <sv@linux.ibm.com>
Subject: Re: [PATCH] powerpc: build-time fixup alternate feature relative addresses
Date: Tue, 12 Mar 2024 07:36:52 +0000 [thread overview]
Message-ID: <59ed9af0-4ea2-4b5d-9b87-db7be883658a@csgroup.eu> (raw)
In-Reply-To: <4af58af4-9fe6-47f6-a896-63c1bb6012ee@linux.vnet.ibm.com>
Le 29/01/2024 à 07:25, Sathvika Vasireddy a écrit :
> Hi Christophe, Nick
>
> On 1/26/24 12:32 AM, Christophe Leroy wrote:
>> Hi Nic,
>>
>> Le 21/05/2017 à 03:01, Nicholas Piggin a écrit :
>>> Implement build-time fixup of alternate feature relative addresses for
>>> the out-of-line ("else") patch code. This is done post-link with a new
>>> powerpc build tool that parses relocations and fixup structures, and
>>> adjusts branch instructions.
>>>
>>> This gives us the ability to link patch code anywhere in the kernel,
>>> without branches to targets outside the patch code having to be
>>> reached directly (without a linker stub). This allows patch code to be
>>> moved out from the head section, and avoids build failures with
>>> unresolvable branche.
>>
>> Is it worth keeping this hanging in patchwork ? It seems outdated and
>> doesn't apply. Could this me done with objtool instead ?
>>
>> Christophe
>
> Yes, this can be done with objtool. I am working on this and will post
> an RFC this week.
>
Nice.
I've open an issue to track his at
https://github.com/linuxppc/issues/issues/479 and have retired Nic's
patch in patchwork.
Christophe
prev parent reply other threads:[~2024-03-12 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-21 1:01 [PATCH] powerpc: build-time fixup alternate feature relative addresses Nicholas Piggin
2024-01-25 19:02 ` Christophe Leroy
[not found] ` <4af58af4-9fe6-47f6-a896-63c1bb6012ee@linux.vnet.ibm.com>
2024-03-12 7:36 ` Christophe Leroy [this message]
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=59ed9af0-4ea2-4b5d-9b87-db7be883658a@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=sv@linux.ibm.com \
--cc=sv@linux.vnet.ibm.com \
/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).