public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Lawrence <joe.lawrence@redhat.com>
To: Sumanth Korikkar <sumanthk@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, hca@linux.ibm.com,
	jpoimboe@kernel.org, gor@linux.ibm.com, iii@linux.ibm.com,
	agordeev@linux.ibm.com
Subject: Re: [PATCH v2 0/4] s390: compile relocatable kernel with/without fPIE
Date: Fri, 21 Jun 2024 12:59:21 -0400	[thread overview]
Message-ID: <157b32d5-7e68-a77f-6f72-356433e4a942@redhat.com> (raw)
In-Reply-To: <4610b08d-46a4-b6fc-2ec5-a88abba7022c@redhat.com>

On 6/19/24 14:23, Joe Lawrence wrote:
> On 6/19/24 13:01, Sumanth Korikkar wrote:
>> Other Note:
>> The latest kernel is built with -fPIC and linked with -no-pie (reference
>> commit: ca888b17da9b ("s390: Compile kernel with -fPIC and link with
>> -no-pie")) which also avoids generation of dynamic symbols and helps
>> kpatch usecases (when num of sections >=64k sections).  Also the build
>> options would be similar (-fPIC in kernel and -fPIC in kpatch-build)
>>
>> For latest kernel, there is no need to add explicit -fPIC again
>> in kpatch tool.
>>
>> But for the intermediate commits, yes, makes sense to add
>> it in kpatch-build tools and will create one PR.
>>
> 
> Interesting!  With 00cda11d3b2e ("s390: Compile kernel with -fPIC and
> link with -no-pie") it sounds like the original vmlinux would be built
> with -fPIC as well, so the optimization decisions re: __mmput() would
> likely be the same.  I can retry the tests with v6.10-rcX to verify.
> 

To follow up, all of the kpatch-build integration tests work with
v6.10.0-rc4 :) as the kernel is built with -fPIC and so are the kpatch
reference and patched builds.  For pre-v6.10 kernels, I think there may
be some instances where a patch author may need to account for slight
build differences to appease kpatch-build expectations as I noticed here.

-- 
Joe


  parent reply	other threads:[~2024-06-21 16:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 13:27 [PATCH v2 0/4] s390: compile relocatable kernel with/without fPIE Sumanth Korikkar
2024-02-19 13:27 ` [PATCH v2 1/4] s390/vdso64: filter out munaligned-symbols flag for vdso Sumanth Korikkar
2024-02-19 13:27 ` [PATCH v2 2/4] s390: Add relocs tool Sumanth Korikkar
2024-02-19 16:11   ` Heiko Carstens
2024-02-19 13:27 ` [PATCH v2 3/4] s390: Compile relocatable kernel without -fPIE Sumanth Korikkar
2024-02-19 13:27 ` [PATCH v2 4/4] s390/kernel: vmlinux.lds.S: handle orphan .rela sections Sumanth Korikkar
2024-02-19 16:12 ` [PATCH v2 0/4] s390: compile relocatable kernel with/without fPIE Heiko Carstens
2024-06-18 20:37 ` Joe Lawrence
2024-06-19 17:01   ` Sumanth Korikkar
2024-06-19 18:23     ` Joe Lawrence
2024-06-21  7:14       ` Sumanth Korikkar
2024-06-21 11:32         ` Joe Lawrence
2024-06-21 16:59       ` Joe Lawrence [this message]
2024-06-24  9:59         ` Sumanth Korikkar

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=157b32d5-7e68-a77f-6f72-356433e4a942@redhat.com \
    --to=joe.lawrence@redhat.com \
    --cc=agordeev@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=iii@linux.ibm.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=sumanthk@linux.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