From: Segher Boessenkool <segher@kernel.crashing.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Rohan McLure <rmclure@linux.ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"npiggin@gmail.com" <npiggin@gmail.com>
Subject: Re: [PATCH v2 11/14] powerpc/64s: Clear/restore caller gprs in syscall interrupt/return
Date: Thu, 11 Aug 2022 10:47:51 -0500 [thread overview]
Message-ID: <20220811154751.GG25951@gate.crashing.org> (raw)
In-Reply-To: <cd3f5a35-dfda-ef2e-dd13-93d5c4011f16@csgroup.eu>
On Thu, Aug 11, 2022 at 03:39:58PM +0000, Christophe Leroy wrote:
>
>
> Le 11/08/2022 à 17:13, Segher Boessenkool a écrit :
> > Hi!
> >
> > On Mon, Jul 25, 2022 at 04:31:11PM +1000, Rohan McLure wrote:
> >> + /*
> >> + * Zero user registers to prevent influencing speculative execution
> >> + * state of kernel code.
> >> + */
> >> + NULLIFY_GPRS(5, 12)
> >> + NULLIFY_NVGPRS()
> >
> > "Nullify" means "invalidate", which is not what this does or is for :-(
>
> Would "Zeroise" be more appropriate ?
That is probably a good compromise, yes. It obviously is a verb, its
meaning is clear and unamiguous, and there is precedent for it even :-)
Thanks,
Segher
next prev parent reply other threads:[~2022-08-11 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 6:31 [PATCH v2 11/14] powerpc/64s: Clear/restore caller gprs in syscall interrupt/return Rohan McLure
2022-08-11 10:11 ` Andrew Donnellan
2022-08-15 0:29 ` Rohan McLure
2022-08-11 15:13 ` Segher Boessenkool
2022-08-11 15:39 ` Christophe Leroy
2022-08-11 15:47 ` Segher Boessenkool [this message]
2022-08-14 23:59 ` Rohan McLure
2022-08-19 6:22 ` 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=20220811154751.GG25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--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).