From: Peter Maydell <peter.maydell@linaro.org>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Meador Inge <meadori@codesourcery.com>,
Paul Brook <paul@codesourcery.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH v2 1/1] gdbserver: Don't send a GDB syscall until the system CPU is stopped
Date: Tue, 6 Mar 2012 19:05:51 +0000 [thread overview]
Message-ID: <CAFEAcA_p6q4sPU1fBV9rvGNR=UNZNGeZW9-Vva8XN6eK2PP3tg@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-jP-8xNpgiPWRru0d=KC9588ZPZQ_U9V_qPpJVNOE28Q@mail.gmail.com>
Ping? Who commits gdbstub patches?
-- PMM
On 20 February 2012 16:18, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 17 February 2012 16:21, Meador Inge <meadori@codesourcery.com> wrote:
>> Fix an issue where the GDB server implementation was sending GDB syscall
>> requests while the system CPU was still running. Syscall requests must
>> be sent while the CPU is stopped otherwise replies from the GDB client
>> might get dropped and the GDB server might be incorrectly transitioned
>> into a 'RUN_STATE_PAUSED' state.
>>
>> Signed-off-by: Meador Inge <meadori@codesourcery.com>
>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
>
> I can confirm that this fixes the "read/write syscalls stall" issue
> I was seeing with your previous patch.
>
> -- PMM
prev parent reply other threads:[~2012-03-06 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 16:21 [Qemu-devel] [PATCH v2 0/1] Fix GDB semihosting Meador Inge
2012-02-17 16:21 ` [Qemu-devel] [PATCH v2 1/1] gdbserver: Don't send a GDB syscall until the system CPU is stopped Meador Inge
2012-02-20 16:18 ` Peter Maydell
2012-03-06 19:05 ` Peter Maydell [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='CAFEAcA_p6q4sPU1fBV9rvGNR=UNZNGeZW9-Vva8XN6eK2PP3tg@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=anthony@codemonkey.ws \
--cc=meadori@codesourcery.com \
--cc=paul@codesourcery.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).