From: Rich Felker <dalias@libc.org>
To: Kevin <kevin@liao.gg>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [PATCH] Add clock_gettime VDSO support for Riscv64
Date: Tue, 17 Sep 2024 16:43:07 -0400 [thread overview]
Message-ID: <20240917204307.GG10433@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAAi9v1kpNPQ_mvL0uw0cLuVfhBQCDjd3McMeMS1jebhfpxo7eA@mail.gmail.com>
On Wed, Sep 18, 2024 at 02:08:02AM +0800, Kevin wrote:
> Hello,
>
> Currently, musl on Riscv64 does not implement VDSO for the clock_gettime
> function call. The following patch should fix it. (Rudimentary testing on a
> Riscv64 virtual machine confirms this works.) A similar patch could
> probably be made for Riscv32. This patch was made based on information
> from: https://man7.org/linux/man-pages/man7/vdso.7.html
>
> Please CC me on replies.
>
> ---
> arch/riscv64/syscall_arch.h | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/arch/riscv64/syscall_arch.h b/arch/riscv64/syscall_arch.h
> index 7fd042cd..81993fc8 100644
> --- a/arch/riscv64/syscall_arch.h
> +++ b/arch/riscv64/syscall_arch.h
> @@ -71,8 +71,7 @@ static inline long __syscall6(long n, long a, long b,
> long c, long d, long e, lo
> }
>
> #define VDSO_USEFUL
> -/* We don't have a clock_gettime function.
> #define VDSO_CGT_SYM "__vdso_clock_gettime"
> -#define VDSO_CGT_VER "LINUX_2.6" */
> +#define VDSO_CGT_VER "LINUX_4.15"
>
> #define IPC_64 0
> --
> 2.34.1
If I understand correctly, the problem isn't that we didn't have it
but that the symbol version string was wrong so it wasn't used?
I have another pending patch for ppc[64] and s390x to add vdso, so it
would be nice to get rv fixed too. Thanks.
Rich
prev parent reply other threads:[~2024-09-17 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 18:08 Kevin
2024-09-17 20:43 ` Rich Felker [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=20240917204307.GG10433@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=kevin@liao.gg \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).