qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: qemu-devel@nongnu.org
Cc: floss@arusekk.pl
Subject: [PATCH v4 0/4] linux-user: Add syscall dispatch support
Date: Thu,  4 Sep 2025 12:23:06 +0200	[thread overview]
Message-ID: <20250904102311.57383-1-richard.henderson@linaro.org> (raw)

Hiya,

I have adjusted the signal return trampoline detection from

  https://lore.kernel.org/qemu-devel/20250711225226.14652-1-floss@arusekk.pl/

and tidied up a few other bits.  Would you please re-test this
versus your plan9 emulator?  Thanks,


r~


Arusekk (1):
  linux-user: Add syscall dispatch support

Richard Henderson (3):
  linux-user: Create vdso_sigreturn_region_{start,end}
  linux-user: Populate sigreturn_region_{start,end} in all vdso.S
  linux-user: Populate vdso_sigreturn_region_{start,end} from sigtramp
    page

 linux-user/loader.h            |   2 +
 linux-user/qemu.h              |   5 +++
 linux-user/signal-common.h     |   7 +++
 linux-user/syscall_defs.h      |   6 +++
 linux-user/elfload.c           |   7 +++
 linux-user/gen-vdso.c          |   6 +++
 linux-user/main.c              |   2 +
 linux-user/signal.c            |   2 +
 linux-user/syscall.c           |  76 ++++++++++++++++++++++++++++++++-
 linux-user/aarch64/vdso-be.so  | Bin 3224 -> 3320 bytes
 linux-user/aarch64/vdso-le.so  | Bin 3224 -> 3320 bytes
 linux-user/aarch64/vdso.S      |   2 +
 linux-user/arm/vdso-be32.so    | Bin 2648 -> 2724 bytes
 linux-user/arm/vdso-be8.so     | Bin 2648 -> 2724 bytes
 linux-user/arm/vdso-le.so      | Bin 2648 -> 2724 bytes
 linux-user/arm/vdso.S          |   2 +
 linux-user/gen-vdso-elfn.c.inc |   7 ++-
 linux-user/hppa/vdso.S         |   2 +
 linux-user/hppa/vdso.so        | Bin 2104 -> 2224 bytes
 linux-user/i386/vdso.S         |   2 +
 linux-user/i386/vdso.so        | Bin 2672 -> 2792 bytes
 linux-user/loongarch64/vdso.S  |   2 +
 linux-user/loongarch64/vdso.so | Bin 3560 -> 3712 bytes
 linux-user/ppc/vdso-32.so      | Bin 3020 -> 3140 bytes
 linux-user/ppc/vdso-64.so      | Bin 3896 -> 4048 bytes
 linux-user/ppc/vdso-64le.so    | Bin 3896 -> 4048 bytes
 linux-user/ppc/vdso.S          |   2 +
 linux-user/riscv/vdso-32.so    | Bin 2980 -> 3124 bytes
 linux-user/riscv/vdso-64.so    | Bin 3944 -> 4104 bytes
 linux-user/riscv/vdso.S        |   2 +
 linux-user/s390x/vdso.S        |   2 +
 linux-user/s390x/vdso.so       | Bin 3464 -> 3616 bytes
 32 files changed, 133 insertions(+), 3 deletions(-)

-- 
2.43.0



             reply	other threads:[~2025-09-04 10:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04 10:23 Richard Henderson [this message]
2025-09-04 10:23 ` [PATCH v4 1/4] linux-user: Create vdso_sigreturn_region_{start,end} Richard Henderson
2025-09-04 10:23 ` [PATCH v4 2/4] linux-user: Populate sigreturn_region_{start, end} in all vdso.S Richard Henderson
2025-09-04 10:23 ` [PATCH v4 3/4] linux-user: Populate vdso_sigreturn_region_{start, end} from sigtramp page Richard Henderson
2025-09-04 10:23 ` [PATCH v4 4/4] linux-user: Add syscall dispatch support Richard Henderson
2025-09-19  7:54 ` [PATCH v4 0/4] " Arusekk
2025-09-19 12:58   ` Richard Henderson

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=20250904102311.57383-1-richard.henderson@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=floss@arusekk.pl \
    --cc=qemu-devel@nongnu.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).