All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: qemu-devel@nongnu.org
Cc: Nicholas Piggin <npiggin@gmail.com>, Warner Losh <imp@bsdimp.com>,
	Kyle Evans <kevans@freebsd.org>,
	Laurent Vivier <laurent@vivier.eu>,
	Pierrick Bouvier <pierrick.bouvier@linaro.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Alistair Francis <alistair.francis@wdc.com>,
	Weiwei Li <liwei1518@gmail.com>,
	Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
	Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
	qemu-riscv@nongnu.org
Subject: [PATCH 0/3] Fix missing and incorrect unlock_user calls
Date: Sat, 21 Mar 2026 10:48:33 +1000	[thread overview]
Message-ID: <20260321004836.500390-1-npiggin@gmail.com> (raw)

This fixes a few tree-wide issues I found when implementing
vector state signal handling for riscv.

Thanks,
Nick

Nicholas Piggin (3):
  bsd-user: Fix unlock_user API usage
  linux-user: Fix unlock_user API usage
  linux-user: riscv: Fix signal frame user mapping

 bsd-user/bsd-misc.c       | 2 +-
 bsd-user/bsd-misc.h       | 2 +-
 bsd-user/bsdload.c        | 2 +-
 linux-user/linuxload.c    | 2 +-
 linux-user/riscv/signal.c | 1 +
 linux-user/syscall.c      | 6 +++---
 6 files changed, 8 insertions(+), 7 deletions(-)

-- 
2.51.0



             reply	other threads:[~2026-03-21  0:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-21  0:48 Nicholas Piggin [this message]
2026-03-21  0:48 ` [PATCH 1/3] bsd-user: Fix unlock_user API usage Nicholas Piggin
2026-03-21  4:17   ` Warner Losh
2026-03-21  0:48 ` [PATCH 2/3] linux-user: " Nicholas Piggin
2026-03-22  6:54   ` Chao Liu
2026-03-26  6:01     ` Nicholas Piggin
2026-03-25  1:46   ` Alistair Francis
2026-03-26  6:20     ` Nicholas Piggin
2026-03-21  0:48 ` [PATCH 3/3] linux-user: riscv: Fix signal frame user mapping Nicholas Piggin
2026-03-22  6:44   ` Chao Liu
2026-03-25  1:53   ` Alistair Francis

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=20260321004836.500390-1-npiggin@gmail.com \
    --to=npiggin@gmail.com \
    --cc=alistair.francis@wdc.com \
    --cc=dbarboza@ventanamicro.com \
    --cc=imp@bsdimp.com \
    --cc=kevans@freebsd.org \
    --cc=laurent@vivier.eu \
    --cc=liwei1518@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=pierrick.bouvier@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=zhiwei_liu@linux.alibaba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.