Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Yao Qi <yao@codesourcery.com>
Subject: Re: [RFA 5/8] New port: TI C6x: gdb port
Date: Thu, 04 Aug 2011 19:48:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1108041937420.31451@digraph.polyomino.org.uk> (raw)
In-Reply-To: <201108041845.35876.pedro@codesourcery.com>

On Thu, 4 Aug 2011, Pedro Alves wrote:

> > Won't GDB need a list of how the register names correspond to DWARF 
> > register numbers (which are allocated for all these registers) somewhere?
> 
> AFAICS, gdbserver only exposes A0-A15, CSR, PC, A16-A31
> B16-B31, TSR, ILC, RILC, so I assumed all other registers would be
> system dependent non general purpose control registers, but it's
> probably then that they are only not "user space" registers, and will
> be acessible by bare metal probes/stubs?  Linux programs won't access
> those, right?  I now browsed the ABI's dwarf section and I got that
> impression.

I expect most of them are bare metal only - and I don't suppose they are 
particularly likely to appear in debug info either, but GDB may as well 
know the numbers since they are assigned.

Some of the others *can* however be read/written from userspace (the 
documentation of the MVC instruction gives details, for the documented 
control registers).  (The default in the ABI is for control registers to 
be caller-save.)

Looking at the list of control registers, I'd think that at least AMR, 
GFPGFR, GPLYA, GPLYB, FADCR, FAUCR, FMCR, SSR are plausibly relevant to 
userspace - userspace code using inline assembly or intrinsics, anyway - 
and ought to be available from gdbserver (which might of course require 
kernel changes to expose them to ptrace).

-- 
Joseph S. Myers
joseph@codesourcery.com


  reply	other threads:[~2011-08-04 19:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20  2:10 Yao Qi
2011-07-25 11:32 ` Yao Qi
2011-08-03  1:15   ` ping: " Yao Qi
2011-08-04 12:34 ` Pedro Alves
2011-08-04 15:11   ` Joseph S. Myers
2011-08-04 17:45     ` Pedro Alves
2011-08-04 19:48       ` Joseph S. Myers [this message]
2011-08-05  2:13       ` Yao Qi
2011-08-06  2:26   ` Yao Qi
2011-08-08 13:04     ` Pedro Alves
2011-08-09  2:52       ` Yao Qi
2011-08-09 14:01         ` Pedro Alves
2011-08-09 15:16           ` Yao Qi
2011-08-09 15:42             ` Pedro Alves
2011-08-10  2:37               ` Yao Qi
2011-08-10 13:44                 ` Pedro Alves

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=Pine.LNX.4.64.1108041937420.31451@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=yao@codesourcery.com \
    /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