All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 2/2] gdbstub: Fix vCont behaviour
Date: Thu, 27 Oct 2016 12:40:58 +0100	[thread overview]
Message-ID: <6ff5fd4e-d371-f204-371a-07edcb545e93@redhat.com> (raw)
In-Reply-To: <bdf0a741-6854-19f6-0413-f6f21c5055ca@de.ibm.com>

On 10/26/2016 08:56 AM, Christian Borntraeger wrote:
> On 10/14/2016 01:53 PM, Claudio Imbrenda wrote:
>> When GDB issues a "vCont", QEMU was not handling it correctly when
>> multiple VCPUs are active.
>> For vCont, for each thread (VCPU), it can be specified whether to
>> single step, continue or stop that thread. The default is to stop a
>> thread.

Or more accurately, to leave it stopped as it was.

>> However, when (for example) "vCont;s:2" is issued, all VCPUs continue
>> to run, although all but VCPU nr 2 are to be stopped.

> 
> Any gdbstub expert in the house?

I'm not a qemu gdbstub expert, but FYI, seeing this reminded me to push
to gdb's master a (getting old) gdb patch that clarifies how vCont actions
should be interpreted:

 https://sourceware.org/ml/gdb-patches/2016-02/msg00493.html

It's already live at:

 https://sourceware.org/gdb/current/onlinedocs/gdb/Packets.html

(The "already running" case is for non-stop mode, which qemu
probably doesn't support.)

Thanks,
Pedro Alves

  reply	other threads:[~2016-10-27 11:57 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14 11:53 [Qemu-devel] [PATCH v2 0/2] Qemu: gdbstub: fix vCont Claudio Imbrenda
2016-10-14 11:53 ` [Qemu-devel] [PATCH v2 1/2] move vm_start to cpus.c Claudio Imbrenda
2016-10-19  8:29   ` Christian Borntraeger
2017-01-27 16:31   ` Alex Bennée
2017-01-27 16:54     ` Claudio Imbrenda
2017-01-27 17:05       ` Alex Bennée
2017-01-27 17:16         ` Claudio Imbrenda
2016-10-14 11:53 ` [Qemu-devel] [PATCH v2 2/2] gdbstub: Fix vCont behaviour Claudio Imbrenda
2016-10-26  7:56   ` Christian Borntraeger
2016-10-27 11:40     ` Pedro Alves [this message]
2016-10-28 13:35       ` Claudio Imbrenda
2016-10-28 14:01         ` Pedro Alves
2016-10-28 14:25           ` Claudio Imbrenda
2016-11-02 14:50             ` Pedro Alves
2017-01-27 16:49   ` Alex Bennée
2017-01-27 17:07   ` Alex Bennée
2017-01-27 17:19     ` Claudio Imbrenda
2017-01-27 17:33       ` Alex Bennée

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=6ff5fd4e-d371-f204-371a-07edcb545e93@redhat.com \
    --to=palves@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=imbrenda@linux.vnet.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.