qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel <qemu-devel@nongnu.org>,
	David Hildenbrand <dahi@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2] gdb: provide the name of the architecture in the target.xml
Date: Thu, 21 Jan 2016 17:28:16 +0100	[thread overview]
Message-ID: <20160121172816.72cddd51.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <56A10481.1020009@de.ibm.com>

On Thu, 21 Jan 2016 17:17:05 +0100
Christian Borntraeger <borntraeger@de.ibm.com> wrote:

> On 01/15/2016 03:18 PM, Peter Maydell wrote:
> > On 14 January 2016 at 14:27, Christian Borntraeger
> > <borntraeger@de.ibm.com> wrote:
> >> Ping?
> >>
> >> On 12/03/2015 01:14 PM, Christian Borntraeger 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 is provided by a callback that can
> >>> be implemented by all architectures. The arm implementation has
> >>> special handling for iwmmxt and returns arm otherwise. This can
> >>> be extended if necessary.
> >>>
> >>> Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
> >>> Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>
> >>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> >>> [rework to use a callback]
> >>> ---
> >>> v1->v2: replace the fixed string with a callback
> >>>
> >>>  gdbstub.c                   | 21 ++++++++++++++-------
> >>>  include/qom/cpu.h           |  3 +++
> >>>  target-arm/cpu.c            | 12 ++++++++++++
> >>>  target-arm/cpu64.c          |  6 ++++++
> >>>  target-ppc/translate_init.c | 10 ++++++++++
> >>>  target-s390x/cpu.c          |  6 ++++++
> >>>  6 files changed, 51 insertions(+), 7 deletions(-)
> > 
> > Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
> > 
> > (at least for the generic and ARM related bits).
> 
> Ok, so I will take that and send it via the s390/kvm tree?
> Well, Conny will probably do the next round.

Will do, unless somebody objects.

      reply	other threads:[~2016-01-21 16:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-03 12:14 [Qemu-devel] [PATCH v2] gdb: provide the name of the architecture in the target.xml Christian Borntraeger
2016-01-14 14:27 ` Christian Borntraeger
2016-01-15 14:18   ` Peter Maydell
2016-01-21 16:17     ` Christian Borntraeger
2016-01-21 16:28       ` Cornelia Huck [this message]

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=20160121172816.72cddd51.cornelia.huck@de.ibm.com \
    --to=cornelia.huck@de.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=dahi@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).