qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Jens Freimann <jfrei@linux.vnet.ibm.com>,
	Alexander Graf <agraf@suse.de>,
	Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] s390x/gdb: various fixes
Date: Mon, 01 Sep 2014 12:06:04 +0200	[thread overview]
Message-ID: <5404450C.1070409@de.ibm.com> (raw)
In-Reply-To: <1409320338-63098-1-git-send-email-jfrei@linux.vnet.ibm.com>

On 29/08/14 15:52, Jens Freimann wrote:
> Conny, Alex, Christian,
> 
> here are some patches improving our gdb support. 
> 
> * Patch 1 fixes a bug where the cc was changed accidentally. 
> * Patch 2 adds the gdb feature XML files for s390x
> * Patch 3 Define acr and fpr registers as coprocessor registers. This allows us
>    to reuse the feature XML files. 
> * Patch 4 whitespace fixes
> * Patch 5 changes common code and other architectures with gdb target.xml support.
>    It adds a field gdb_arch_name to the XML description of the CPU and to struct
>    CPUClass.  It allows the remote gdb to detect the target architecture
>    in cases where it can't tell otherwise.
> 
> David Hildenbrand (5):
>   s390x/gdb: don't touch the cc if tcg is not enabled
>   s390x/gdb: add the feature xml files for s390x
>   s390x/gdb: generate target.xml and handle fp/ac as coprocessors
>   s390x/gdb: coding style fixes
>   gdb: provide the name of the architecture in the target.xml
> 
>  configure                   |   1 +
>  gdb-xml/s390-acr.xml        |  26 +++++++++++
>  gdb-xml/s390-fpr.xml        |  27 +++++++++++
>  gdb-xml/s390x-core64.xml    |  28 ++++++++++++
>  gdbstub.c                   |  19 +++++---
>  include/qom/cpu.h           |   2 +
>  target-arm/cpu64.c          |   1 +
>  target-ppc/translate_init.c |   2 +
>  target-s390x/cpu-qom.h      |   1 +
>  target-s390x/cpu.c          |   5 +-
>  target-s390x/cpu.h          |  40 +---------------
>  target-s390x/gdbstub.c      | 109 +++++++++++++++++++++++++++++++++-----------
>  12 files changed, 188 insertions(+), 73 deletions(-)
>  create mode 100644 gdb-xml/s390-acr.xml
>  create mode 100644 gdb-xml/s390-fpr.xml
>  create mode 100644 gdb-xml/s390x-core64.xml
> 

Applied 1-4.

Peter,
do you want to push patch5 yourself?
As an alternative I can push it via the s390 tree, I need your ACK in that case.

Alex, (or Alexey?) can you ACK/NACK patch 5 from the power perspective? 

  parent reply	other threads:[~2014-09-01 10:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 13:52 [Qemu-devel] [PATCH 0/5] s390x/gdb: various fixes Jens Freimann
2014-08-29 13:52 ` [Qemu-devel] [PATCH 1/5] s390x/gdb: don't touch the cc if tcg is not enabled Jens Freimann
2014-09-01 22:39   ` Alexander Graf
2014-09-02  7:07     ` Christian Borntraeger
2014-09-03  9:27       ` Alexander Graf
2014-09-05  7:29         ` Christian Borntraeger
2014-08-29 13:52 ` [Qemu-devel] [PATCH 2/5] s390x/gdb: add the feature xml files for s390x Jens Freimann
2014-08-29 13:52 ` [Qemu-devel] [PATCH 3/5] s390x/gdb: generate target.xml and handle fp/ac as coprocessors Jens Freimann
2014-08-29 13:52 ` [Qemu-devel] [PATCH 4/5] s390x/gdb: coding style fixes Jens Freimann
2014-08-29 13:52 ` [Qemu-devel] [PATCH 5/5] gdb: provide the name of the architecture in the target.xml Jens Freimann
2014-09-01 10:19   ` Peter Maydell
2014-09-01 10:25     ` Andreas Färber
2014-09-01 10:31     ` Christian Borntraeger
2014-09-01 10:32       ` Peter Maydell
2014-09-03  9:37     ` David Hildenbrand
2014-09-03  9:45       ` Edgar E. Iglesias
2014-09-03  9:59         ` David Hildenbrand
2014-09-03 10:00           ` Edgar E. Iglesias
2014-09-01 10:06 ` Christian Borntraeger [this message]
2014-09-01 22:43   ` [Qemu-devel] [PATCH 0/5] s390x/gdb: various fixes Alexander Graf

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=5404450C.1070409@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=cornelia.huck@de.ibm.com \
    --cc=jfrei@linux.vnet.ibm.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 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).