From: Richard Henderson <richard.henderson@linaro.org>
To: Vineet Gupta <vineetg@rivosinc.com>, qemu-devel@nongnu.org
Cc: "Alistair Francis" <alistair.francis@wdc.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Edwin Lu" <ewlu@rivosinc.com>,
gnu-toolchain <gnu-toolchain@rivosinc.com>,
"Palmer Dabbelt" <palmer@rivosinc.com>
Subject: Re: [PULL 15/21] linux-user/riscv: Add vdso
Date: Sat, 13 Jan 2024 11:05:27 +1100 [thread overview]
Message-ID: <db63ee9b-901a-48ab-beca-4275e12a88d0@linaro.org> (raw)
In-Reply-To: <b84e0809-669f-49c9-8163-847485cfe7e4@rivosinc.com>
On 1/13/24 10:37, Vineet Gupta wrote:
>
>
> On 1/12/24 13:35, Richard Henderson wrote:
>> On 1/12/24 08:49, Vineet Gupta wrote:
>>> Hi Richard, Alistair
>>>
>>> On 10/30/23 14:17, Richard Henderson wrote:
>>>> diff --git a/linux-user/riscv/Makefile.vdso b/linux-user/riscv/Makefile.vdso
>>>> new file mode 100644
>>>> index 0000000000..2c257dbfda
>>>> --- /dev/null
>>>> +++ b/linux-user/riscv/Makefile.vdso
>>>> @@ -0,0 +1,15 @@
>>>> +include $(BUILD_DIR)/tests/tcg/riscv64-linux-user/config-target.mak
>>>> +
>>>> +SUBDIR = $(SRC_PATH)/linux-user/riscv
>>>> +VPATH += $(SUBDIR)
>>>> +
>>>> +all: $(SUBDIR)/vdso-32.so $(SUBDIR)/vdso-64.so
>>>> +
>>>> +LDFLAGS = -nostdlib -shared -fpic -Wl,-h,linux-vdso.so.1 -Wl,--build-id=sha1 \
>>>> + -Wl,--hash-style=both -Wl,-T,$(SUBDIR)/vdso.ld
>>>> +
>>>> +$(SUBDIR)/vdso-32.so: vdso.S vdso.ld vdso-asmoffset.h
>>>> + $(CC) -o $@ $(LDFLAGS) -mabi=ilp32d -march=rv32g $<
>>>> +
>>>> +$(SUBDIR)/vdso-64.so: vdso.S vdso.ld vdso-asmoffset.h
>>>> + $(CC) -o $@ $(LDFLAGS) -mabi=lp64d -march=rv64g $<
>>> So by default qemu ships the vdso binary. How can one rebuild it ?
>>>
>>> From skimming the build files it seems following ought to do it
>>> make update-linux-vdso
>>>
>>> with a prior configure cmd like below with PATH pointing to the cross
>>> compiler.
>>> ../configure --target-list=riscv64-linux-user
>>> --cross-cc-riscv64=riscv64-unknown-linux-gnu-gcc
>> Yes, that should do it.
>>
>>> But it doesn't, I'm sure we are missing something basis here.
>> Do you get an error message?
>> Did $(BUILD_DIR)/tests/tcg/riscv64-linux-user/config-target.mak get created properly?
>
> It was indeed, but invoking make wasn't doing anything.
Odd. It Just Works here...
What do you have in the "Cross compilers" section of the configure output?
I would expect '--cross-prefix-riscv64=...' to be a better option that just gcc. And if
you have it installed as "riscv64-linux-gnu-", I would not expect you to need to provide
any configure option at all -- it should be auto-detected.
next prev parent reply other threads:[~2024-01-13 0:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 21:17 [PULL 00/21] linux-user patch queue Richard Henderson
2023-10-30 21:17 ` [PULL 01/21] linux-user: Fix guest signal remapping after adjusting SIGABRT Richard Henderson
2023-10-30 21:17 ` [PULL 02/21] linux-user: Introduce imgsrc_read, imgsrc_read_alloc Richard Henderson
2023-10-30 21:17 ` [PULL 03/21] linux-user: Tidy loader_exec Richard Henderson
2023-10-30 21:17 ` [PULL 04/21] linux-user: Do not clobber bprm_buf swapping ehdr Richard Henderson
2023-10-30 21:17 ` [PULL 05/21] linux-user: Use ImageSource in load_elf_image Richard Henderson
2023-10-30 21:17 ` [PULL 06/21] linux-user: Use ImageSource in load_symbols Richard Henderson
2023-10-30 21:17 ` [PULL 07/21] linux-user: Replace bprm->fd with bprm->src.fd Richard Henderson
2023-10-30 21:17 ` [PULL 08/21] linux-user: Load vdso image if available Richard Henderson
2023-10-30 21:17 ` [PULL 09/21] linux-user: Add gen-vdso tool Richard Henderson
2023-11-02 12:49 ` Peter Maydell
2023-10-30 21:17 ` [PULL 10/21] linux-user/i386: Add vdso Richard Henderson
2023-10-30 21:17 ` [PULL 11/21] linux-user/x86_64: " Richard Henderson
2023-10-30 21:17 ` [PULL 12/21] linux-user/aarch64: " Richard Henderson
2023-10-30 21:17 ` [PULL 13/21] linux-user/arm: " Richard Henderson
2023-10-30 21:17 ` [PULL 14/21] linux-user/hppa: " Richard Henderson
2023-10-30 21:17 ` [PULL 15/21] linux-user/riscv: " Richard Henderson
2024-01-11 21:49 ` Vineet Gupta
2024-01-12 21:35 ` Richard Henderson
2024-01-12 23:04 ` Palmer Dabbelt
2024-01-12 23:37 ` Vineet Gupta
2024-01-12 23:58 ` Vineet Gupta
2024-01-13 0:05 ` Richard Henderson [this message]
2024-01-13 0:22 ` Vineet Gupta
2024-01-14 23:52 ` Richard Henderson
2023-10-30 21:17 ` [PULL 16/21] linux-user/loongarch64: " Richard Henderson
2023-10-30 21:17 ` [PULL 17/21] linux-user/ppc: " Richard Henderson
2023-10-30 21:17 ` [PULL 18/21] linux-user/s390x: Rename __SIGNAL_FRAMESIZE to STACK_FRAME_OVERHEAD Richard Henderson
2023-10-30 21:17 ` [PULL 19/21] linux-user/s390x: Add vdso Richard Henderson
2023-10-30 21:17 ` [PULL 20/21] linux-user: Show vdso address in /proc/pid/maps Richard Henderson
2023-10-30 21:17 ` [PULL 21/21] build: Add update-linux-vdso makefile rule Richard Henderson
2023-10-31 7:51 ` [PULL 00/21] linux-user patch queue Stefan Hajnoczi
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=db63ee9b-901a-48ab-beca-4275e12a88d0@linaro.org \
--to=richard.henderson@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=ewlu@rivosinc.com \
--cc=gnu-toolchain@rivosinc.com \
--cc=palmer@rivosinc.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=vineetg@rivosinc.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).