From: "Yigael Fleishman" <igal.fl@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: qemu-devel@nongnu.org, frederic.roussel@access-company.com
Subject: Re: [Qemu-devel] Missing system calls retries in case of EINTR
Date: Wed, 11 Jul 2007 10:57:10 -0700 [thread overview]
Message-ID: <a315cb3c0707111057r40b0c1bbvbd1d22c21f1daaac@mail.gmail.com> (raw)
In-Reply-To: <200707111304.33631.rob@landley.net>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
Rob
Thanks for the background info. I wasn't very specific in my last question.
Actually I meant to ask why doesn't qemu code set sigaction(SA_RESTART) for
_all_ signals when running in system emulation mode (or maybe it does, which
means there's even larger problem...)
--Yigael
On 7/11/07, Rob Landley <rob@landley.net> wrote:
>
> Talking about sigaction(SA_RESTART) vs looping around -EINTR everywhere:
>
> On Tuesday 10 July 2007 8:57:34 pm Yigael Fleishman wrote:
> > Rob,
> > Thanks, that should also work.
> > Seems do_sigaction() in linux-user/signal.c has some code which does
> that
> > (though obviously not for the signal that I'm receiving).
> > Any idea why SA_RESTART calls are not invoked by default to restart
> > syscalls for all signals?
>
> Fallout from old 1980's-era Unixes that didn't implement SA_RESTART,
> basically. Standards like SUSv3 say to humor them, because they paid for
> the
> standard...
>
> http://www.ussg.iu.edu/hypermail/linux/kernel/0507.1/1065.html
>
> > --Yigael
>
> Rob
> --
> "One of my most productive days was throwing away 1000 lines of code."
> - Ken Thompson.
>
[-- Attachment #2: Type: text/html, Size: 1582 bytes --]
prev parent reply other threads:[~2007-07-11 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 0:14 [Qemu-devel] Missing system calls retries in case of EINTR Yigael Fleishman
2007-07-06 18:57 ` Rob Landley
2007-07-11 0:57 ` Yigael Fleishman
2007-07-11 17:04 ` Rob Landley
2007-07-11 17:57 ` Yigael Fleishman [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=a315cb3c0707111057r40b0c1bbvbd1d22c21f1daaac@mail.gmail.com \
--to=igal.fl@gmail.com \
--cc=frederic.roussel@access-company.com \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
/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).