qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Jens Freimann <jfrei@linux.vnet.ibm.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Alexander Graf <agraf@suse.de>,
	qemu-devel@nongnu.org,
	David Hildenbrand <dahi@linux.vnet.ibm.com>,
	"Vassili Karpov (malc)" <av1474@comtv.ru>,
	Edgar Iglesias <edgar.iglesias@gmail.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] gdb: provide the name of the architecture in the target.xml
Date: Mon, 6 Oct 2014 17:08:07 +0200	[thread overview]
Message-ID: <20141006170807.4f48fcf8.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <1412090627-18709-2-git-send-email-jfrei@linux.vnet.ibm.com>

On Tue, 30 Sep 2014 17:23:47 +0200
Jens Freimann <jfrei@linux.vnet.ibm.com> wrote:

> From: David Hildenbrand <dahi@linux.vnet.ibm.com>
> 
> This patch provides the name of the architecture in the target.xml if available.
> 
> This allows the remote gdb to detect the target architecture on its own - so
> there is no need to specify it manually (e.g. if gdb is started without a
> binary) using "set arch *arch_name*".
> 
> The name of the architecture has been added to all archs that provide a
> target.xml (by supplying a gdb_core_xml_file) and have a unique architecture
> name in gdb's feature xml files.
> 
> Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
> Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> Acked-by: Christian Borntraeger <borntraeger@de.ibm.com>
> Signed-off-by: Jens Freimann <jfrei@linux.vnet.ibm.com>
> Reviewed-by: Andreas Färber <afaerber@suse.de>
> Cc: Andrzej Zaborowski <balrogg@gmail.com>
> Cc: Peter Maydell <peter.maydell@linaro.org>
> Cc: Vassili Karpov (malc) <av1474@comtv.ru>
> CC: Edgar Iglesias <edgar.iglesias@gmail.com>
> CC: Richard Henderson <rth@twiddle.net>
> ---
>  gdbstub.c                   | 19 ++++++++++++-------
>  include/qom/cpu.h           |  2 ++
>  target-arm/cpu64.c          |  1 +
>  target-ppc/translate_init.c |  2 ++
>  target-s390x/cpu.c          |  1 +
>  5 files changed, 18 insertions(+), 7 deletions(-)
> 
I will send this with the next pile of s390x updates, unless someone on
cc: has any objections.

  reply	other threads:[~2014-10-06 15:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 15:23 [Qemu-devel] [PATCH] gdb: detect target architecture via target.xml Jens Freimann
2014-09-30 15:23 ` [Qemu-devel] [PATCH] gdb: provide the name of the architecture in the target.xml Jens Freimann
2014-10-06 15:08   ` Cornelia Huck [this message]
2014-10-06 16:57     ` Peter Maydell
2014-10-06 19:14       ` David Hildenbrand
2014-10-06 19:39         ` Peter Maydell
2014-10-06 19:56           ` David Hildenbrand
2014-10-06 17:14   ` Peter Maydell
2014-10-06 19:44     ` David Hildenbrand

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=20141006170807.4f48fcf8.cornelia.huck@de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=agraf@suse.de \
    --cc=av1474@comtv.ru \
    --cc=borntraeger@de.ibm.com \
    --cc=dahi@linux.vnet.ibm.com \
    --cc=edgar.iglesias@gmail.com \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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).