From: Peter Wu <peter@lekensteyn.nl>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
QEMU Trivial <qemu-trivial@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] gdbstub: avoid busy loop while waiting for gdb
Date: Thu, 5 May 2016 18:08:06 +0200 [thread overview]
Message-ID: <20160505160806.GA1044@al> (raw)
In-Reply-To: <CAFEAcA93StM0HME9urYAFKYrhEBxHBCP0+v_RSsSRcvz91=xcg@mail.gmail.com>
On Thu, May 05, 2016 at 04:37:40PM +0100, Peter Maydell wrote:
> On 3 May 2016 at 23:58, Peter Wu <peter@lekensteyn.nl> wrote:
> > While waiting for a gdb response, or while sending an acknowledgement
> > there is not much to do, so just mark the socket as non-blocking to
> > avoid a busy loop while paused at gdb. This only affects the user-mode
> > emulation (qemu-arm -g 1234 ./a.out).
> >
> > Note that this issue was reported before at
> > https://lists.nongnu.org/archive/html/qemu-devel/2013-02/msg02277.html.
> >
> > While at it, close the gdb client fd on EOF or error while reading.
>
> The commit message says "mark the socket as non-blocking"...
>
> > @@ -1599,8 +1603,6 @@ static void gdb_accept(void)
> > gdb_has_xml = false;
> >
> > gdbserver_state = s;
> > -
> > - fcntl(fd, F_SETFL, O_NONBLOCK);
> > }
>
> ...but the code change is *removing* a call to mark the
> socket as non-blocking. Which is correct?
>
> thanks
> -- PMM
The commit message is misleading, it should have been "so do not mark
the socket as non-blocking". If you were to apply this, please fix it up
:-)
--
Kind regards,
Peter Wu
https://lekensteyn.nl
next prev parent reply other threads:[~2016-05-05 16:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 22:58 [Qemu-devel] [PATCH] gdbstub: avoid busy loop while waiting for gdb Peter Wu
2016-05-05 15:37 ` Peter Maydell
2016-05-05 16:08 ` Peter Wu [this message]
2016-05-05 16:23 ` Peter Maydell
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=20160505160806.GA1044@al \
--to=peter@lekensteyn.nl \
--cc=peter.maydell@linaro.org \
--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 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).