From: Laurent Vivier <laurent@vivier.eu>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org,
"qemu-trivial@nongnu.org" <qemu-trivial@nongnu.org>
Subject: Re: [PATCH 3/3] linux-user: Return void from queue_signal()
Date: Tue, 18 Jan 2022 12:42:59 +0100 [thread overview]
Message-ID: <11f9cfb4-138d-01e1-df55-e82eaaf1fb96@vivier.eu> (raw)
In-Reply-To: <20220114153732.3767229-4-peter.maydell@linaro.org>
Le 14/01/2022 à 16:37, Peter Maydell a écrit :
> The linux-user queue_signal() function always returns 1, and none of
> its callers check the return value. Give it a void return type
> instead.
>
> The return value is a leftover from the old pre-2016 linux-user
> signal handling code, which really did have a queue of signals and so
> might return a failure indication if too many signals were queued at
> once. The current design avoids having to ever have more than one
> signal queued via queue_signal() at once, so it can never fail.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> linux-user/signal-common.h | 4 ++--
> linux-user/signal.c | 5 ++---
> 2 files changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/linux-user/signal-common.h b/linux-user/signal-common.h
> index 42aa479080b..2113165a758 100644
> --- a/linux-user/signal-common.h
> +++ b/linux-user/signal-common.h
> @@ -59,8 +59,8 @@ void setup_rt_frame(int sig, struct target_sigaction *ka,
>
> void process_pending_signals(CPUArchState *cpu_env);
> void signal_init(void);
> -int queue_signal(CPUArchState *env, int sig, int si_type,
> - target_siginfo_t *info);
> +void queue_signal(CPUArchState *env, int sig, int si_type,
> + target_siginfo_t *info);
> void host_to_target_siginfo(target_siginfo_t *tinfo, const siginfo_t *info);
> void target_to_host_siginfo(siginfo_t *info, const target_siginfo_t *tinfo);
> int target_to_host_signal(int sig);
> diff --git a/linux-user/signal.c b/linux-user/signal.c
> index bfbbeab9ad2..32854bb3752 100644
> --- a/linux-user/signal.c
> +++ b/linux-user/signal.c
> @@ -780,8 +780,8 @@ static void QEMU_NORETURN dump_core_and_abort(int target_sig)
>
> /* queue a signal so that it will be send to the virtual CPU as soon
> as possible */
> -int queue_signal(CPUArchState *env, int sig, int si_type,
> - target_siginfo_t *info)
> +void queue_signal(CPUArchState *env, int sig, int si_type,
> + target_siginfo_t *info)
> {
> CPUState *cpu = env_cpu(env);
> TaskState *ts = cpu->opaque;
> @@ -794,7 +794,6 @@ int queue_signal(CPUArchState *env, int sig, int si_type,
> ts->sync_signal.pending = sig;
> /* signal that a new signal is pending */
> qatomic_set(&ts->signal_pending, 1);
> - return 1; /* indicates that the signal was queued */
> }
>
>
Applied to my trivial-patches branch.
Thanks,
Laurent
prev parent reply other threads:[~2022-01-18 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 15:37 [PATCH 0/3] linux-user: Fix some minor nits Peter Maydell
2022-01-14 15:37 ` [PATCH 1/3] linux-user: Remove unnecessary 'aligned' attribute from TaskState Peter Maydell
2022-01-27 13:20 ` Laurent Vivier
2022-01-14 15:37 ` [PATCH 2/3] linux-user: Rename user_force_sig tracepoint to match function name Peter Maydell
2022-01-14 15:46 ` Philippe Mathieu-Daudé via
2022-01-18 11:41 ` Laurent Vivier
2022-01-14 15:37 ` [PATCH 3/3] linux-user: Return void from queue_signal() Peter Maydell
2022-01-14 15:57 ` Philippe Mathieu-Daudé via
2022-01-18 11:42 ` Laurent Vivier [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=11f9cfb4-138d-01e1-df55-e82eaaf1fb96@vivier.eu \
--to=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).