From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org, "Daniel P. Berrange" <berrange@redhat.com>
Cc: Matthew Bloch <matthew@bytemark.co.uk>, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: [PATCH] Fix freezing bug in curses console
Date: Sun, 1 Mar 2009 13:03:37 +0000 [thread overview]
Message-ID: <200903011303.38741.paul@codesourcery.com> (raw)
In-Reply-To: <20090301113635.GA10538@redhat.com>
> > > I think it still suffers from the same race condition so today it
> > > wouldn't work. You could fix the bottom half scheduling though so that
> > > you could safely schedule a bottom half from a signal handler (using
> > > roughly the same trick).
> >
> > Fwiw, it's perfectly sensible to have a single pipe which is shared by
> > all signal handlers, just used to say "check for work flags set".
>
> And if you need the main loop to be able to distinguish signals coming
> out of the pipe, then just write the signum into the pipe as a byte,
> instead of a single dummy byte. Or even write the whole 'siginfo_t'
> struct passed to the signal handler, and read it out in sizeof(siginfo_t)
> sized chunks for processing.
I don't think this will works. If the pipe buffer gets full the write will
either block or you'll loose signals.
When using the pipe as a simple semaphore all you care about is the presence
or absence of data. It doesn't matter if subsequent writes loose data (e.g.
by not retrying a nonblocking write) as long as a write to an empty pipe
succeeds.
Paul
next prev parent reply other threads:[~2009-03-01 13:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 15:51 [PATCH] Fix freezing bug in curses console Matthew Bloch
2009-02-27 19:49 ` Anthony Liguori
2009-02-27 21:01 ` [Qemu-devel] " andrzej zaborowski
2009-02-27 21:04 ` Anthony Liguori
2009-02-28 21:21 ` Jamie Lokier
2009-03-01 11:36 ` Daniel P. Berrange
2009-03-01 13:03 ` Paul Brook [this message]
2009-03-01 14:07 ` Anthony Liguori
2009-03-02 16:57 ` Jamie Lokier
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=200903011303.38741.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=berrange@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=matthew@bytemark.co.uk \
--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 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.