From: Christophe LYON <christophe.lyon@st.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] ARM/system mode/stdin
Date: Wed, 16 Jun 2010 16:49:34 +0200 [thread overview]
Message-ID: <4C18E47E.8040107@st.com> (raw)
In-Reply-To: <4C16289D.8040708@st.com>
Hi all,
After more investigation, I am wondering whether there is a conflict
between 2 entities reading for stdin:
- one is initialized by qemu_chr_open_stdio() (in qemu-char.c)
- the 2nd one is the handling of SYS_READ in arm-semi.c
After some debug/tracing, I have noticed that a few chars a swallowed
from stdin by calls to stdio_read() because the stdin FD is monitored by
the select() call in main_loop_wait().
This seems to be in conflict with the ARM semihosting support for
SYS_READ which also tries to read FD 0.
If I remove the call to
qemu_set_fd_handler2(0, stdio_read_poll, stdio_read, NULL, chr);
in qemu_chr_open_stdio() then my sample test works, but I wonder what I
might have broken?
Thanks and best regards,
Christophe.
next prev parent reply other threads:[~2010-06-16 14:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 13:03 [Qemu-devel] ARM/system mode/stdin Christophe LYON
2010-06-16 14:49 ` Christophe LYON [this message]
2010-06-18 16:52 ` Paul Brook
2010-06-21 8:34 ` Christophe LYON
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=4C18E47E.8040107@st.com \
--to=christophe.lyon@st.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).