All of lore.kernel.org
 help / color / mirror / Atom feed
From: Claudio Imbrenda <imbrenda@linux.vnet.ibm.com>
To: pbonzini@redhat.com
Cc: qemu-devel@nongnu.org, palves@redhat.com, borntraeger@de.ibm.com
Subject: Re: [Qemu-devel] [PATCH v3 0/2] Qemu: gdbstub: fix vCont
Date: Wed, 30 Nov 2016 16:37:34 +0100	[thread overview]
Message-ID: <9f666405-9458-343a-25e1-bc2b3ee40266@linux.vnet.ibm.com> (raw)
In-Reply-To: <1477674916-6795-1-git-send-email-imbrenda@linux.vnet.ibm.com>

Hi Paolo, I was wondering if you had seen this new version of the vCont
patchset, which I sent around last month -- is there any more work to do
or things to fix? or is it going to be upstreamed after 2.8?
(btw I just rebased it on 2.8.0-rc2 and it applied cleanly)

please don't keep me in suspense :)

thanks!


Claudio


On 28/10/16 19:15, Claudio Imbrenda wrote:
> 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
> 
> 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                     |  44 ++++++++++-
>  gdbstub.c                  | 189 ++++++++++++++++++++++++++++++++++-----------
>  hw/i386/kvmvapic.c         |   2 +
>  include/sysemu/cpus.h      |   1 +
>  include/sysemu/sysemu.h    |   2 +
>  target-s390x/misc_helper.c |   2 +
>  vl.c                       |  32 +-------
>  7 files changed, 195 insertions(+), 77 deletions(-)
> 

  parent reply	other threads:[~2016-11-30 15:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 17:15 [Qemu-devel] [PATCH v3 0/2] Qemu: gdbstub: fix vCont Claudio Imbrenda
2016-10-28 17:15 ` [Qemu-devel] [PATCH v3 1/2] move vm_start to cpus.c Claudio Imbrenda
2017-01-25 10:21   ` Paolo Bonzini
2017-01-25 17:53     ` Claudio Imbrenda
2017-01-25 18:02       ` Paolo Bonzini
2016-10-28 17:15 ` [Qemu-devel] [PATCH v3 2/2] gdbstub: Fix vCont behaviour Claudio Imbrenda
2017-01-25 10:34   ` Paolo Bonzini
2017-01-25 17:55     ` Claudio Imbrenda
2016-11-30 15:37 ` Claudio Imbrenda [this message]
2017-01-12 16:45 ` [Qemu-devel] [PATCH v3 0/2] Qemu: gdbstub: fix vCont Claudio Imbrenda
2017-01-25 10:05   ` Christian Borntraeger
2017-01-25 10:12     ` 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=9f666405-9458-343a-25e1-bc2b3ee40266@linux.vnet.ibm.com \
    --to=imbrenda@linux.vnet.ibm.com \
    --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 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.