qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ilya Leoshkevich <iii@linux.ibm.com>
To: "Richard Henderson" <richard.henderson@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Laurent Vivier" <laurent@vivier.eu>
Cc: qemu-devel@nongnu.org, Michael Tokarev <mjt@tls.msk.ru>,
	Brian Cain <bcain@quicinc.com>,
	"ltaylorsimpson @ gmail . com" <ltaylorsimpson@gmail.com>,
	Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH v3 0/2] linux-user: Allow mapping low priority rt signals
Date: Wed, 30 Oct 2024 00:17:46 +0100	[thread overview]
Message-ID: <20241029232211.206766-1-iii@linux.ibm.com> (raw)

v1: Unfortunately lost.

v2: https://lore.kernel.org/qemu-devel/20240212205022.242968-1-iii@linux.ibm.com/
v2 -> v3: Make the mapping configurable (Richard).

Hi,

There are apps out there that want to use SIGRTMAX, which linux-user
currently does not map to a host signal. The reason is that with the
current approach it's not possible to map all target signals, so it
was decided to sacrifice the end of the range.

This series improves the situation by making the mapping configurable.
Patch 1 is the implementation, patch 2 is a test.

Best regards,
Ilya

Ilya Leoshkevich (2):
  linux-user: Allow custom rt signal mappings
  tests/tcg: Add SIGRTMIN/SIGRTMAX test

 linux-user/main.c                             |  12 +-
 linux-user/signal-common.h                    |   2 +-
 linux-user/signal.c                           | 108 ++++++++++++++----
 meson.build                                   |   3 +-
 meson_options.txt                             |   2 +
 scripts/meson-buildoptions.sh                 |   2 +
 tests/tcg/Makefile.target                     |   4 +-
 tests/tcg/multiarch/linux/linux-sigrtminmax.c |  74 ++++++++++++
 8 files changed, 182 insertions(+), 25 deletions(-)
 create mode 100644 tests/tcg/multiarch/linux/linux-sigrtminmax.c

-- 
2.47.0



             reply	other threads:[~2024-10-29 23:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 23:17 Ilya Leoshkevich [this message]
2024-10-29 23:17 ` [PATCH v3 1/2] linux-user: Allow custom rt signal mappings Ilya Leoshkevich
2024-10-31 14:35   ` Richard Henderson
2024-10-29 23:17 ` [PATCH v3 2/2] tests/tcg: Add SIGRTMIN/SIGRTMAX test Ilya Leoshkevich
2024-11-04 20:52 ` [PATCH v3 0/2] linux-user: Allow mapping low priority rt signals 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=20241029232211.206766-1-iii@linux.ibm.com \
    --to=iii@linux.ibm.com \
    --cc=alex.bennee@linaro.org \
    --cc=bcain@quicinc.com \
    --cc=laurent@vivier.eu \
    --cc=ltaylorsimpson@gmail.com \
    --cc=mjt@tls.msk.ru \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).