From: Yvan Roux <yvan.roux@foss.st.com>
To: Luis Machado <luis.machado@arm.com>, <gdb-patches@sourceware.org>
Cc: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
Subject: Re: [PATCH] gdb/arm: Only stack S16..S31 when FPU registers are secure
Date: Wed, 29 Jun 2022 11:52:43 +0200 [thread overview]
Message-ID: <20220629095243.GA30810@gnbcxd0114.gnb.st.com> (raw)
In-Reply-To: <d8cc7f2e-f339-4a90-00fe-c9100bb2b50e@arm.com>
On Tue, Jun 21, 2022 at 03:19:52PM +0100, Luis Machado wrote:
> Hi,
>
> Sorry I missed this one.
>
> On 6/14/22 15:47, Yvan Roux wrote:
> > Hi,
> >
> > The FPCCR.TS bit is used to identify if FPU registers are considered
> > non-secure or secure. If they are secure, then callee saved registers
>
> Two spaces after `.`.
>
> > (S16 to S31) are stacked on exception entry or otherwise skipped.
> >
> > Signed-off-by: Torbj�rn SVENSSON <torbjorn.svensson@foss.st.com>
> > Signed-off-by: Yvan Roux <yvan.roux@foss.st.com>
> > ---
> > gdb/arch/arm.h | 6 ++++++
> > gdb/arm-tdep.c | 9 ++++++++-
> > 2 files changed, 14 insertions(+), 1 deletion(-)
> >
> > diff --git a/gdb/arch/arm.h b/gdb/arch/arm.h
> > index 4ad329f6f1f..de1b472fe71 100644
> > --- a/gdb/arch/arm.h
> > +++ b/gdb/arch/arm.h
> > @@ -136,6 +136,12 @@ enum arm_m_profile_type {
> > #define XPSR_T 0x01000000
> > +/* System control registers addresses. */
> > +
>
> Maybe we should make it a bit more verbose. How about...
>
> /* System control registers accessible through an address. */
>
> > +/* M-profile Floating-Point Context Control Register address, defined in ARMv7-M
> > + (Section B3.2.2) and ARMv8-M (Section D1.2.99) reference manuals. */
> > +#define FPCCR 0xE000EF34
> > +
>
> Since these are effectively addresses, I wonder if we should create an enum category for
> them, with a type that is really the type used to store an address, as opposed to storing a
> register number.
>
> enum class system_register_address: CORE_ADDR
> {
> FPCCR = 0xe000ef34,
> };
>
> What do you think?
I agree, but I'd use an unscoped enum to avoid having to use a static_cast when
using it.
>
> > /* Size of registers. */
> > #define ARM_INT_REGISTER_SIZE 4
> > diff --git a/gdb/arm-tdep.c b/gdb/arm-tdep.c
> > index 456649afdaa..abc812817aa 100644
> > --- a/gdb/arm-tdep.c
> > +++ b/gdb/arm-tdep.c
> > @@ -3519,6 +3519,13 @@ arm_m_exception_cache (struct frame_info *this_frame)
> > {
> > int i;
> > int fpu_regs_stack_offset;
> > + ULONGEST fpccr;
> > + bool fpccr_ts;
>
> Define the above during assignment.
>
> > +
> > + /* Read FPCCR register */
> > + gdb_assert (safe_read_memory_unsigned_integer (FPCCR, 4, byte_order,
> > + &fpccr));
>
> 4 -> ARM_INT_REGISTER_SIZE?
>
> > + fpccr_ts = fpccr & (1 << 26);
>
> Just a suggestion. How about having a function that extracts the bit, since we're really interested
> if the bit is set or not, and not in the position of the bit.
There is a macro for that purpose, so let's using it ;)
>
> > /* This code does not take into account the lazy stacking, see "Lazy
> > context save of FP state", in B1.5.7, also ARM AN298, supported
> > @@ -3538,7 +3545,7 @@ arm_m_exception_cache (struct frame_info *this_frame)
> > cache->saved_regs[ARM_FPSCR_REGNUM].set_addr (unwound_sp + sp_r0_offset + 0x60);
> > fpu_regs_stack_offset += 4;
> > - if (tdep->have_sec_ext && !default_callee_register_stacking)
> > + if (tdep->have_sec_ext && !default_callee_register_stacking && fpccr_ts)
> > {
> > /* Handle floating-point callee saved registers. */
> > fpu_regs_stack_offset = unwound_sp + sp_r0_offset + 0x68;
>
Here is the new version of the patch:
The FPCCR.TS bit is used to identify if FPU registers are considered
non-secure or secure. If they are secure, then callee saved registers
(S16 to S31) are stacked on exception entry or otherwise skipped.
Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>
---
gdb/arch/arm.h | 9 +++++++++
gdb/arm-tdep.c | 9 ++++++++-
2 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/gdb/arch/arm.h b/gdb/arch/arm.h
index 4ad329f6f1f..36757493406 100644
--- a/gdb/arch/arm.h
+++ b/gdb/arch/arm.h
@@ -109,6 +109,15 @@ enum arm_m_profile_type {
ARM_M_TYPE_INVALID
};
+/* System control registers accessible through an addresses. */
+enum system_register_address : CORE_ADDR
+{
+ /* M-profile Floating-Point Context Control Register address, defined in
+ ARMv7-M (Section B3.2.2) and ARMv8-M (Section D1.2.99) reference
+ manuals. */
+ FPCCR = 0xe000ef34
+};
+
/* Instruction condition field values. */
#define INST_EQ 0x0
#define INST_NE 0x1
diff --git a/gdb/arm-tdep.c b/gdb/arm-tdep.c
index e36bde9b3da..8330e819ccb 100644
--- a/gdb/arm-tdep.c
+++ b/gdb/arm-tdep.c
@@ -3573,6 +3573,13 @@ arm_m_exception_cache (struct frame_info *this_frame)
{
int i;
int fpu_regs_stack_offset;
+ ULONGEST fpccr;
+
+ /* Read FPCCR register. */
+ gdb_assert (safe_read_memory_unsigned_integer (FPCCR,
+ ARM_INT_REGISTER_SIZE,
+ byte_order, &fpccr));
+ bool fpccr_ts = bit(fpccr,26);
/* This code does not take into account the lazy stacking, see "Lazy
context save of FP state", in B1.5.7, also ARM AN298, supported
@@ -3592,7 +3599,7 @@ arm_m_exception_cache (struct frame_info *this_frame)
cache->saved_regs[ARM_FPSCR_REGNUM].set_addr (unwound_sp + sp_r0_offset + 0x60);
fpu_regs_stack_offset += 4;
- if (tdep->have_sec_ext && !default_callee_register_stacking)
+ if (tdep->have_sec_ext && !default_callee_register_stacking && fpccr_ts)
{
/* Handle floating-point callee saved registers. */
fpu_regs_stack_offset = unwound_sp + sp_r0_offset + 0x68;
--
2.17.1
next prev parent reply other threads:[~2022-06-29 9:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 14:47 Yvan Roux
2022-06-21 14:19 ` Luis Machado
2022-06-29 9:52 ` Yvan Roux [this message]
2022-06-29 10:55 ` Luis Machado
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=20220629095243.GA30810@gnbcxd0114.gnb.st.com \
--to=yvan.roux@foss.st.com \
--cc=gdb-patches@sourceware.org \
--cc=luis.machado@arm.com \
--cc=torbjorn.svensson@foss.st.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).