public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Evan Green <evan@rivosinc.com>
To: libc-alpha@sourceware.org
Cc: vineetg@rivosinc.com, slewis@rivosinc.com, palmer@rivosinc.com,
	Florian Weimer <fweimer@redhat.com>,
	Evan Green <evan@rivosinc.com>
Subject: [PATCH v10 2/7] linux: Introduce INTERNAL_VSYSCALL
Date: Wed, 13 Dec 2023 13:11:37 -0800	[thread overview]
Message-ID: <20231213211142.1543025-3-evan@rivosinc.com> (raw)
In-Reply-To: <20231213211142.1543025-1-evan@rivosinc.com>

Add an INTERNAL_VSYSCALL() macro that makes a vDSO call, falling back to
a regular syscall, but without setting errno. Instead, the return value
is plumbed straight out of the macro.

Signed-off-by: Evan Green <evan@rivosinc.com>
---

Changes in v10:
 - Introduced INTERNAL_VSYSCALL patch

 sysdeps/unix/sysv/linux/sysdep-vdso.h | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/sysdeps/unix/sysv/linux/sysdep-vdso.h b/sysdeps/unix/sysv/linux/sysdep-vdso.h
index a51b5deb37..2a1fc17e23 100644
--- a/sysdeps/unix/sysv/linux/sysdep-vdso.h
+++ b/sysdeps/unix/sysv/linux/sysdep-vdso.h
@@ -53,4 +53,23 @@
     sc_ret;								      \
   })
 
+#define INTERNAL_VSYSCALL(name, nr, args...)				      \
+  ({									      \
+    __label__ out;							      \
+    long int sc_ret;							      \
+									      \
+    __typeof (GLRO(dl_vdso_##name)) vdsop = GLRO(dl_vdso_##name);	      \
+    if (vdsop != NULL)							      \
+      {									      \
+	sc_ret = INTERNAL_VSYSCALL_CALL (vdsop, nr, ##args);	      	      \
+	if ((!INTERNAL_SYSCALL_ERROR_P (sc_ret)) ||			      \
+	    (INTERNAL_SYSCALL_ERRNO (sc_ret) != ENOSYS))		      \
+	  goto out;							      \
+      }									      \
+									      \
+    sc_ret = INTERNAL_SYSCALL_CALL (name, ##args);		      	      \
+  out:									      \
+    sc_ret;								      \
+  })
+
 #endif /* SYSDEP_VDSO_LINUX_H  */
-- 
2.34.1


  parent reply	other threads:[~2023-12-13 21:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 21:11 [PATCH v10 0/7] RISC-V: ifunced memcpy using new kernel hwprobe interface Evan Green
2023-12-13 21:11 ` [PATCH v10 1/7] riscv: Add Linux hwprobe syscall support Evan Green
2023-12-13 21:11 ` Evan Green [this message]
2023-12-13 21:11 ` [PATCH v10 3/7] riscv: Add hwprobe vdso call support Evan Green
2023-12-13 21:11 ` [PATCH v10 4/7] riscv: Add __riscv_hwprobe pointer to ifunc calls Evan Green
2023-12-13 21:11 ` [PATCH v10 5/7] riscv: Enable multi-arg ifunc resolvers Evan Green
2023-12-13 21:11 ` [PATCH v10 6/7] riscv: Add ifunc helper method to hwprobe.h Evan Green
2024-01-08 18:53   ` Adhemerval Zanella Netto
2023-12-13 21:11 ` [PATCH v10 7/7] riscv: Add and use alignment-ignorant memcpy Evan Green
2024-01-08 18:56   ` Adhemerval Zanella Netto
2024-01-08 17:06 ` [PATCH v10 0/7] RISC-V: ifunced memcpy using new kernel hwprobe interface Evan Green
2024-01-08 18:10   ` Palmer Dabbelt
2024-01-09 12:06   ` Stefan O'Rear
2024-01-09 17:10     ` Evan Green
2024-01-09 18:29       ` Stefan O'Rear
2024-01-09 18:41         ` Evan Green
2024-01-09 19:09           ` Stefan O'Rear
2024-01-09 19:18             ` enh
2024-01-09 19:36             ` Evan Green

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=20231213211142.1543025-3-evan@rivosinc.com \
    --to=evan@rivosinc.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=palmer@rivosinc.com \
    --cc=slewis@rivosinc.com \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).