linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Donnellan <ajd@linux.ibm.com>
To: Rohan McLure <rmclure@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: npiggin@gmail.com
Subject: Re: [PATCH v2 09/14] powerpc: Add NULLIFY_GPRS macros for register clears
Date: Mon, 08 Aug 2022 17:42:41 +1000	[thread overview]
Message-ID: <7b6439f8288d71306e63d89f145597d1327afc35.camel@linux.ibm.com> (raw)
In-Reply-To: <20220725062906.120088-1-rmclure@linux.ibm.com>

On Mon, 2022-07-25 at 16:29 +1000, Rohan McLure wrote:
> Macros for restoring and saving registers to and from the stack
> exist.
> Provide macros with the same interface for clearing a range of gprs
> by
> setting each register's value in that range to zero.
> 
> The resulting macros are called NULLIFY_GPRS and NULLIFY_NVGPRS,
> keeping
> with the naming of the accompanying restore and save macros, and
> usage
> of nullify to describe this operation elsewhere in the kernel.
> 
> Signed-off-by: Rohan McLure <rmclure@linux.ibm.com>
> ---
> V1 -> V2: Change 'ZERO' usage in naming to 'NULLIFY', a more obvious
> verb

And I see you've addressed my comment re 32 v 64 bit from V1 as well.

Reviewed-by: Andrew Donnellan <ajd@linux.ibm.com>

> ---
>  arch/powerpc/include/asm/ppc_asm.h | 22 ++++++++++++++++++++++
>  1 file changed, 22 insertions(+)
> 
> diff --git a/arch/powerpc/include/asm/ppc_asm.h
> b/arch/powerpc/include/asm/ppc_asm.h
> index 83c02f5a7f2a..d6c46082bf7f 100644
> --- a/arch/powerpc/include/asm/ppc_asm.h
> +++ b/arch/powerpc/include/asm/ppc_asm.h
> @@ -33,6 +33,20 @@
>         .endr
>  .endm
>  
> +/*
> + * This expands to a sequence of register clears for regs start to
> end
> + * inclusive, of the form:
> + *
> + *   li rN, 0
> + */
> +.macro NULLIFY_REGS start, end
> +       .Lreg=\start
> +       .rept (\end - \start + 1)
> +       li      .Lreg, 0
> +       .Lreg=.Lreg+1
> +       .endr
> +.endm
> +

I suppose this could be done using the existing OP_REGS macro,
something like OP_REGS li, 0, start, end, 0, 0 - but a load immediate
is semantically a bit different from the existing uses of OP_REGS so I
don't mind either way

>  /*
>   * Macros for storing registers into and loading registers from
>   * exception frames.
> @@ -49,6 +63,14 @@
>  #define REST_NVGPRS(base)              REST_GPRS(13, 31, base)
>  #endif
>  
> +#define        NULLIFY_GPRS(start, end)        NULLIFY_REGS start,
> end
> +#ifdef __powerpc64__
> +#define        NULLIFY_NVGPRS()                NULLIFY_GPRS(14, 31)
> +#else
> +#define        NULLIFY_NVGPRS()                NULLIFY_GPRS(13, 31)
> +#endif
> +#define        NULLIFY_GPR(n)                  NULLIFY_GPRS(n, n)
> +
>  #define SAVE_GPR(n, base)              SAVE_GPRS(n, n, base)
>  #define REST_GPR(n, base)              REST_GPRS(n, n, base)
>  

-- 
Andrew Donnellan    OzLabs, ADL Canberra
ajd@linux.ibm.com   IBM Australia Limited


  reply	other threads:[~2022-08-08  7:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25  6:29 [PATCH v2 09/14] powerpc: Add NULLIFY_GPRS macros for register clears Rohan McLure
2022-08-08  7:42 ` Andrew Donnellan [this message]
2022-08-08 10:55   ` Christophe Leroy

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=7b6439f8288d71306e63d89f145597d1327afc35.camel@linux.ibm.com \
    --to=ajd@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=npiggin@gmail.com \
    --cc=rmclure@linux.ibm.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 NNTP newsgroup(s).