From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: qemu-trivial@nongnu.org, Jan Kiszka <jan.kiszka@siemens.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] Use SIGIO with caution
Date: Tue, 31 May 2011 08:47:25 -0500 [thread overview]
Message-ID: <4DE4F16D.6030009@codemonkey.ws> (raw)
In-Reply-To: <1306705831-59385-1-git-send-email-andreas.faerber@web.de>
On 05/29/2011 04:50 PM, Andreas Färber wrote:
> BeOS and Haiku don't define SIGIO. When undefined, it won't arrive
> and doesn't need to be blocked.
>
> Signed-off-by: Andreas Färber<andreas.faerber@web.de>
Anything to do with signal masks is never a trivial patch BTW...
But I actually think explicit handling of SIGIO is unneeded. I think
this is a hold over from the pre-I/O thread days where we selectively
set SIGIO on certain file descriptors to make sure that when an IO fd
became readable, we received a signal to break out of the KVM emulation
loop.
Can the folks on CC confirm/deny?
I can't see any use of SIGIO in the current source tree.
Regards,
Anthony Liguori
> ---
> cpus.c | 8 ++++++++
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/cpus.c b/cpus.c
> index 1fc34b7..42af291 100644
> --- a/cpus.c
> +++ b/cpus.c
> @@ -395,7 +395,9 @@ static int qemu_signal_init(void)
> pthread_sigmask(SIG_UNBLOCK,&set, NULL);
>
> sigemptyset(&set);
> +#ifdef SIGIO
> sigaddset(&set, SIGIO);
> +#endif
> sigaddset(&set, SIGALRM);
> sigaddset(&set, SIG_IPI);
> sigaddset(&set, SIGBUS);
> @@ -408,7 +410,9 @@ static int qemu_signal_init(void)
> * We need to process timer signals synchronously to avoid a race
> * between exit_request check and KVM vcpu entry.
> */
> +#ifdef SIGIO
> sigaddset(&set, SIGIO);
> +#endif
> sigaddset(&set, SIGALRM);
> }
> #endif
> @@ -449,12 +453,16 @@ static void qemu_kvm_init_cpu_signals(CPUState *env)
> #else
> sigemptyset(&set);
> sigaddset(&set, SIG_IPI);
> +#ifdef SIGIO
> sigaddset(&set, SIGIO);
> +#endif
> sigaddset(&set, SIGALRM);
> pthread_sigmask(SIG_BLOCK,&set, NULL);
>
> pthread_sigmask(SIG_BLOCK, NULL,&set);
> +#ifdef SIGIO
> sigdelset(&set, SIGIO);
> +#endif
> sigdelset(&set, SIGALRM);
> #endif
> sigdelset(&set, SIG_IPI);
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <andreas.faerber@web.de>
Cc: qemu-trivial@nongnu.org, Jan Kiszka <jan.kiszka@siemens.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Use SIGIO with caution
Date: Tue, 31 May 2011 08:47:25 -0500 [thread overview]
Message-ID: <4DE4F16D.6030009@codemonkey.ws> (raw)
In-Reply-To: <1306705831-59385-1-git-send-email-andreas.faerber@web.de>
On 05/29/2011 04:50 PM, Andreas Färber wrote:
> BeOS and Haiku don't define SIGIO. When undefined, it won't arrive
> and doesn't need to be blocked.
>
> Signed-off-by: Andreas Färber<andreas.faerber@web.de>
Anything to do with signal masks is never a trivial patch BTW...
But I actually think explicit handling of SIGIO is unneeded. I think
this is a hold over from the pre-I/O thread days where we selectively
set SIGIO on certain file descriptors to make sure that when an IO fd
became readable, we received a signal to break out of the KVM emulation
loop.
Can the folks on CC confirm/deny?
I can't see any use of SIGIO in the current source tree.
Regards,
Anthony Liguori
> ---
> cpus.c | 8 ++++++++
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/cpus.c b/cpus.c
> index 1fc34b7..42af291 100644
> --- a/cpus.c
> +++ b/cpus.c
> @@ -395,7 +395,9 @@ static int qemu_signal_init(void)
> pthread_sigmask(SIG_UNBLOCK,&set, NULL);
>
> sigemptyset(&set);
> +#ifdef SIGIO
> sigaddset(&set, SIGIO);
> +#endif
> sigaddset(&set, SIGALRM);
> sigaddset(&set, SIG_IPI);
> sigaddset(&set, SIGBUS);
> @@ -408,7 +410,9 @@ static int qemu_signal_init(void)
> * We need to process timer signals synchronously to avoid a race
> * between exit_request check and KVM vcpu entry.
> */
> +#ifdef SIGIO
> sigaddset(&set, SIGIO);
> +#endif
> sigaddset(&set, SIGALRM);
> }
> #endif
> @@ -449,12 +453,16 @@ static void qemu_kvm_init_cpu_signals(CPUState *env)
> #else
> sigemptyset(&set);
> sigaddset(&set, SIG_IPI);
> +#ifdef SIGIO
> sigaddset(&set, SIGIO);
> +#endif
> sigaddset(&set, SIGALRM);
> pthread_sigmask(SIG_BLOCK,&set, NULL);
>
> pthread_sigmask(SIG_BLOCK, NULL,&set);
> +#ifdef SIGIO
> sigdelset(&set, SIGIO);
> +#endif
> sigdelset(&set, SIGALRM);
> #endif
> sigdelset(&set, SIG_IPI);
next prev parent reply other threads:[~2011-05-31 13:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-29 21:50 [Qemu-trivial] [PATCH] Use SIGIO with caution Andreas Färber
2011-05-29 21:50 ` [Qemu-devel] " Andreas Färber
2011-05-31 13:47 ` Anthony Liguori [this message]
2011-05-31 13:47 ` Anthony Liguori
2011-05-31 14:06 ` [Qemu-trivial] " Jan Kiszka
2011-05-31 14:06 ` Jan Kiszka
2011-05-31 14:26 ` [Qemu-trivial] " Anthony Liguori
2011-05-31 14:26 ` Anthony Liguori
2011-05-31 14:54 ` [Qemu-trivial] " Jan Kiszka
2011-05-31 14:54 ` Jan Kiszka
2011-05-31 15:44 ` [Qemu-trivial] " Alexander Graf
2011-05-31 15:44 ` Alexander Graf
2011-05-31 15:48 ` [Qemu-trivial] " Anthony Liguori
2011-05-31 15:48 ` Anthony Liguori
2011-05-31 16:16 ` [Qemu-trivial] " Alexander Graf
2011-05-31 16:16 ` Alexander Graf
2011-05-31 19:49 ` [Qemu-trivial] " Anthony Liguori
2011-05-31 19:49 ` Anthony Liguori
2011-05-31 21:11 ` [Qemu-trivial] " Andreas Färber
2011-05-31 21:11 ` Andreas Färber
2011-05-31 21:43 ` [Qemu-trivial] " Jan Kiszka
2011-05-31 21:43 ` [Qemu-devel] " Jan Kiszka
2011-05-31 23:19 ` [Qemu-trivial] " Anthony Liguori
2011-05-31 23:19 ` [Qemu-devel] " Anthony Liguori
2011-05-31 14:11 ` [Qemu-trivial] " Avi Kivity
2011-05-31 14:11 ` Avi Kivity
2011-05-31 21:24 ` [Qemu-trivial] " Andreas Färber
2011-05-31 21:24 ` Andreas Färber
2011-06-01 22:30 ` [Qemu-trivial] " Stefan Hajnoczi
2011-06-01 22:30 ` [Qemu-devel] [Qemu-trivial] " Stefan Hajnoczi
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=4DE4F16D.6030009@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=andreas.faerber@web.de \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=mtosatti@redhat.com \
--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 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.