From: "Yigael Fleishman" <igal.fl@gmail.com>
To: qemu-devel@nongnu.org
Cc: frederic.roussel@access-company.com
Subject: [Qemu-devel] Missing system calls retries in case of EINTR
Date: Mon, 25 Jun 2007 17:14:24 -0700 [thread overview]
Message-ID: <a315cb3c0706251714nd05f5dbt8ca7fdef25a0f720@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
Running qemu on a Ubuntu Feisty host I've encountered an occasional
failure-to-launch problem.
I've used the "-serial /dev/ttyS0" at the command line, and qemu would often
exit printing "could not open serial device".
Looking in the srcs I've noticed that qemu_chr_open_tty does not retry the
'open' syscall if it fails and errno=EINTR.
I've added a retry for such case and it seems to solve that specific problem
(see the following patch).
Furthermore, I've noticed that all open, read and some write calls in
vl.care not retried in such cases.
It seems to me retries should be implemented in those cases, however I might
still be missing something here.
--- /tmp/p4diff/vl.c#1.32670 2007-06-25 17:04:53.000000000 -0700
+++ vl.c 2007-06-25 17:04:29.000000000 -0700
@@ -1786,9 +1786,19 @@
CharDriverState *chr;
int fd;
- fd = open(filename, O_RDWR | O_NONBLOCK);
- if (fd < 0)
- return NULL;
+ /* The following code wraps the 'open' syscall and retries it in case
it is interrupted. */
+ while (1)
+ {
+ fd = open(filename, O_RDWR | O_NONBLOCK );
+
+ if (fd < 0)
+ {
+ if (errno != EINTR)
+ return NULL;
+ }
+ else
+ break;
+ }
fcntl(fd, F_SETFL, O_NONBLOCK);
tty_serial_init(fd, 115200, 'N', 8, 1);
chr = qemu_chr_open_fd(fd, fd);
[-- Attachment #2: Type: text/html, Size: 2145 bytes --]
next reply other threads:[~2007-06-26 0:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 0:14 Yigael Fleishman [this message]
2007-07-06 18:57 ` [Qemu-devel] Missing system calls retries in case of EINTR Rob Landley
2007-07-11 0:57 ` Yigael Fleishman
2007-07-11 17:04 ` Rob Landley
2007-07-11 17:57 ` Yigael Fleishman
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=a315cb3c0706251714nd05f5dbt8ca7fdef25a0f720@mail.gmail.com \
--to=igal.fl@gmail.com \
--cc=frederic.roussel@access-company.com \
--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 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).