From: Michael Ellerman <mpe@ellerman.id.au>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: C vdso
Date: Sat, 24 Oct 2020 00:24:39 +1100 [thread overview]
Message-ID: <877drhxeg8.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <be21c7c8-6828-b757-064d-20f74e5c1a31@csgroup.eu>
Christophe Leroy <christophe.leroy@csgroup.eu> writes:
> Le 24/09/2020 à 15:17, Christophe Leroy a écrit :
>> Le 17/09/2020 à 14:33, Michael Ellerman a écrit :
>>> Christophe Leroy <christophe.leroy@csgroup.eu> writes:
>>>>
>>>> What is the status with the generic C vdso merge ?
>>>> In some mail, you mentionned having difficulties getting it working on
>>>> ppc64, any progress ? What's the problem ? Can I help ?
>>>
>>> Yeah sorry I was hoping to get time to work on it but haven't been able
>>> to.
>>>
>>> It's causing crashes on ppc64 ie. big endian.
...
>>
>> Can you tell what defconfig you are using ? I have been able to setup a full glibc PPC64 cross
>> compilation chain and been able to test it under QEMU with success, using Nathan's vdsotest tool.
>
> What config are you using ?
ppc64_defconfig + guest.config
Or pseries_defconfig.
I'm using Ubuntu GCC 9.3.0 mostly, but it happens with other toolchains too.
At a minimum we're seeing relocations in the output, which is a problem:
$ readelf -r build\~/arch/powerpc/kernel/vdso64/vdso64.so
Relocation section '.rela.dyn' at offset 0x12a8 contains 8 entries:
Offset Info Type Sym. Value Sym. Name + Addend
000000001368 000000000016 R_PPC64_RELATIVE 7c0
000000001370 000000000016 R_PPC64_RELATIVE 9300
000000001380 000000000016 R_PPC64_RELATIVE 970
000000001388 000000000016 R_PPC64_RELATIVE 9300
000000001398 000000000016 R_PPC64_RELATIVE a90
0000000013a0 000000000016 R_PPC64_RELATIVE 9300
0000000013b0 000000000016 R_PPC64_RELATIVE b20
0000000013b8 000000000016 R_PPC64_RELATIVE 9300
cheers
next prev parent reply other threads:[~2020-10-23 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200916165516.Horde.uocmo3irPb7BMg__NUSqRA9@messagerie.si.c-s.fr>
[not found] ` <87r1r0oa4o.fsf@mpe.ellerman.id.au>
2020-09-24 13:17 ` C vdso Christophe Leroy
2020-10-23 6:28 ` Christophe Leroy
2020-10-23 13:24 ` Michael Ellerman [this message]
2020-10-24 10:07 ` Michael Ellerman
2020-10-24 11:16 ` Christophe Leroy
2020-11-03 18:11 ` Christophe Leroy
2020-11-03 18:13 ` Christophe Leroy
2020-11-24 10:11 ` Christophe Leroy
2020-11-25 2:04 ` Michael Ellerman
2020-11-25 9:21 ` Christophe Leroy
2020-11-25 12:22 ` Michael Ellerman
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=877drhxeg8.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).