From: Segher Boessenkool <segher@kernel•crashing.org>
To: Christophe Leroy <christophe.leroy@c-s•fr>
Cc: linuxppc-dev@lists•ozlabs.org, Joel Stanley <joel@jms•id.au>
Subject: Re: [PATCH] powerpc: vmlinux.lds: Drop Binutils 2.18 workarounds
Date: Thu, 28 Mar 2019 10:11:58 -0500 [thread overview]
Message-ID: <20190328151158.GB3969@gate.crashing.org> (raw)
In-Reply-To: <4ceb12ff-b114-6edd-e9c2-a6cd922720a2@c-s.fr>
On Thu, Mar 28, 2019 at 07:19:57AM +0100, Christophe Leroy wrote:
> Le 27/03/2019 à 19:21, Segher Boessenkool a écrit :
> >Yeah, okay, we should have some PHDRS statement here still. You can drop
> >the dummy segment, and the notes segment as well, or you can keep the notes
> >section in both the notes and kernel segments.
>
> Is the note segment useful at all ? I guess if we decide to keep it, we
> should have a reason.
I don't know if it is.
$ readelf -x17 powerpc64/kernel/vmlinux
Hex dump of section '.notes':
0xc0000000010d4128 00000004 00000014 00000003 474e5500 ............GNU.
0xc0000000010d4138 ba254e47 396b1745 176695d8 6b54c9e3 .%NG9k.E.f..kT..
0xc0000000010d4148 959cedd7 00000006 00000001 00000100 ................
0xc0000000010d4158 4c696e75 78000000 00000000 Linux.......
Does that look useful? There's a build-id in there it seems. I don't know
if any tools look at that, or how they find it.
> >(You patch doesn't apply btw, whitespace damage I think; will you send a
> >new one?)
>
> Originally the patch is by Joel Stanley <joel@jms•id.au>
>
> I guess he will send a v2 taking into account the discussion ?
Please do Joel :-) Thanks in advance, etc.
> Or maybe you can send it yourself as you are probably the best person to
> explain in details the change in the commit message.
I have no way of testing things properly.
Segher
next prev parent reply other threads:[~2019-03-28 15:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 0:32 [PATCH] powerpc: vmlinux.lds: Drop Binutils 2.18 workarounds Joel Stanley
2019-03-21 23:34 ` Segher Boessenkool
2019-03-22 0:22 ` Michael Ellerman
2019-03-26 0:55 ` Michael Ellerman
2019-03-26 7:55 ` Christophe Leroy
2019-03-26 18:19 ` Segher Boessenkool
2019-03-26 19:28 ` Christophe Leroy
2019-03-26 20:12 ` Segher Boessenkool
2019-03-26 22:29 ` Segher Boessenkool
2019-03-26 22:59 ` Segher Boessenkool
2019-03-27 6:40 ` Christophe Leroy
2019-03-27 12:47 ` Segher Boessenkool
2019-03-27 18:21 ` Segher Boessenkool
2019-03-28 6:19 ` Christophe Leroy
2019-03-28 15:11 ` Segher Boessenkool [this message]
2019-03-27 8:56 ` Christophe Leroy
2019-03-27 9:09 ` Christophe Leroy
2019-03-26 8:08 ` Christophe Leroy
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=20190328151158.GB3969@gate.crashing.org \
--to=segher@kernel$(echo .)crashing.org \
--cc=christophe.leroy@c-s$(echo .)fr \
--cc=joel@jms$(echo .)id.au \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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