From: Max Filippov <jcmvbkbc@gmail.com>
To: Marc Gauthier <marc@tensilica.com>
Cc: Maxim Grigoriev <maxim2405@gmail.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: xtensa: reading privileged special registers
Date: Mon, 18 Jul 2011 08:38:00 -0000 [thread overview]
Message-ID: <CAMo8BfJ4_7TkUZu-5O=npHp7j4+tfKasCKhGkiXXs6rx3JcpBA@mail.gmail.com> (raw)
In-Reply-To: <522C1DF17AF50042AD8AE87F7887BD3D01E849DCB7@exch.hq.tensilica.com>
Maxim, Marc, thank you for the answers.
> To see privileged registers, you'd want a setup that can e.g. debug a kernel or raw hardware.
That's my case: I have a gdbserver built into qemu, it has full access
to the processor state.
> For simplicity, the same register set is generated both for user and kernel situations, so GDB lists privileged registers even for user processes (e.g. via gdbserver or Linux native), even though they're not accessible. Maybe one day we'll fix that.
I can try to fix it, but I'm not sure what's the right way. I'd query
these registers from within xtensa_pseudo_register_read and fall back
to returning 0 if that query fails. Does that makes sense?
--
Thanks.
-- Max
next prev parent reply other threads:[~2011-07-18 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-17 20:29 Max Filippov
2011-07-18 1:12 ` Maxim Grigoriev
[not found] ` <CAC3St3DkgTP_bAbpdSh6n3bVivik1tieUopy-jd-yNrEyE=C1A@mail.gmail.com>
2011-07-18 2:00 ` Marc Gauthier
2011-07-18 8:38 ` Max Filippov [this message]
2011-07-18 8:20 ` Max Filippov
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='CAMo8BfJ4_7TkUZu-5O=npHp7j4+tfKasCKhGkiXXs6rx3JcpBA@mail.gmail.com' \
--to=jcmvbkbc@gmail.com \
--cc=gdb@sourceware.org \
--cc=marc@tensilica.com \
--cc=maxim2405@gmail.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