public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@polymtl.ca>
To: Zied Guermazi <zied.guermazi@trande.de>,
	"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: where to put defines for exception numbers as encoded in ARM CoreSight ETM traces
Date: Thu, 18 Mar 2021 23:29:51 -0400	[thread overview]
Message-ID: <c26d53f9-1f76-4758-300a-45acb0556aef@polymtl.ca> (raw)
In-Reply-To: <e5fa0d2d-4821-a709-90ae-e4347b3966dd@trande.de>

> hi
> 
> in ETM traces (3.4 and above), exception encodings for non v7m processors (v7A, is done in a 4 bit field, defined in table 7.12 - (https://developer.arm.com/documentation/ihi0014/q/ETMv3-Signal-Protocol/Instruction-tracing/Branch-Packets?lang=en#BABIECBB <https://developer.arm.com/documentation/ihi0014/q/ETMv3-Signal-Protocol/Instruction-tracing/Branch-Packets?lang=en#BABIECBB>). This is not the same encoding as for exception vector.
> 
> This is needed for handling the implementation of breakpoints as an undefined instruction trap in GDB for ARMv7 while decoding ETM traces (branch tracing extension to use ARM CoreSight ETM)
> 
> what will be a good location for adding defines for this exception encoding? will it be fine to add them in arch/arm.h? shall I create a new header file for them? please advise.
> 
> Kind Regards
> 
> Zied Guermazi

Hi,

I don't know the specific details of this problem, but yes a file under
arch/ sounds fine.  These files contain definitions and helpers shared
between gdb and gdbserver (yes, even though it's under the gdb
directory).

Puting them in arm.h or in a new file are both fine.

Simon

      reply	other threads:[~2021-03-19  3:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-19  0:23 Zied Guermazi
2021-03-19  3:29 ` Simon Marchi [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=c26d53f9-1f76-4758-300a-45acb0556aef@polymtl.ca \
    --to=simon.marchi@polymtl.ca \
    --cc=gdb@sourceware.org \
    --cc=zied.guermazi@trande.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).