qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
To: pbonzini@redhat.com
Cc: borntraeger@de.ibm.com, qemu-devel@nongnu.org, palves@redhat.com,
	alex.bennee@linaro.org
Subject: [Qemu-devel] [PATCH v7 0/2] Qemu: gdbstub: fix vCont
Date: Fri, 27 Jan 2017 19:11:31 +0100	[thread overview]
Message-ID: <1485540693-31723-1-git-send-email-imbrenda@linux.vnet.ibm.com> (raw)

This small patchset fixes the incorrect behaviour of the vCont command
in the gdb stub. 

The first patch, as suggested be Paolo, refactors some code. The most
visible change is that it moves vm_start to cpus.c 

The second one fixes the incorrect behaviour of the vCont command.
Previously, continuing or stepping a single thread (CPU) caused all
other CPUs to be started too, whereas the GDB specification clearly
states that without a default action all threads not explicitly
mentioned in the command should stay stopped.

So if the Qemu gdbstub receives a  vCont;c:1  packet, no other CPU
should be restarted except the first, and when a  vCont;s:1  is
received, the first CPU should be stepped without restarting the others.
With this patchset Qemu now behaves as expected.

See here for reference material about the packets: 
https://sourceware.org/gdb/current/onlinedocs/gdb/Packets.html
https://sourceware.org/gdb/onlinedocs/gdb/Packets.html

v6 -> v7
* fixed description of patch 1 to reflect what is actually happening
  and improved description of patch 2
* removed leftover header declaration of resume_some_vcpus which had
  been removed a few versions ago
* fixed a compilation issue when compiling userspace-mode only
  (global variable max_cpus is not defined when not in system-mode)

v4 -> v6
* rebased on master after target-s390x was moved
* put qemu_clock_enable back into resume_all_vcpus
* improved the parsing function of the vCont packet
* added qemu_clock_enable to gdb_continue_partial

v3 -> v4
* rebased on v2.8.0-rc2, no changes needed

v2 -> v3
* removed resume_some_vcpus
* cleared up the code and simplified the implementation in light of the 
  clarification in the specification of the vCont packet

Claudio Imbrenda (2):
  move vm_start to cpus.c
  gdbstub: Fix vCont behaviour

 cpus.c                  |  42 +++++++++++
 gdbstub.c               | 194 ++++++++++++++++++++++++++++++++++++------------
 include/sysemu/sysemu.h |   2 +
 vl.c                    |  30 +-------
 4 files changed, 192 insertions(+), 76 deletions(-)

-- 
1.9.1

             reply	other threads:[~2017-01-27 18:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-27 18:11 Claudio Imbrenda [this message]
2017-01-27 18:11 ` [Qemu-devel] [PATCH v7 1/2] move vm_start to cpus.c Claudio Imbrenda
2017-02-06  9:53   ` Paolo Bonzini
2017-01-27 18:11 ` [Qemu-devel] [PATCH v7 2/2] gdbstub: Fix vCont behaviour Claudio Imbrenda
2017-02-06 10:00   ` Paolo Bonzini
2017-02-07  9:59     ` Claudio Imbrenda
2017-02-07 15:10       ` Paolo Bonzini

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=1485540693-31723-1-git-send-email-imbrenda@linux.vnet.ibm.com \
    --to=imbrenda@linux.vnet.ibm.com \
    --cc=alex.bennee@linaro.org \
    --cc=borntraeger@de.ibm.com \
    --cc=palves@redhat.com \
    --cc=pbonzini@redhat.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).