From: Andrew Donnellan <ajd@linux.ibm.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Michael Ellerman <mpe@ellerman.id.au>,
rmclure@linux.ibm.com
Cc: david@redhat.com, linux-kernel@vger.kernel.org,
wsa+renesas@sang-engineering.com, nicholas@linux.ibm.com,
windhl@126.com, cuigaosheng1@huawei.com, mikey@neuling.org,
paul@paul-moore.com, aneesh.kumar@linux.ibm.com,
haren@linux.ibm.com, joel@jms.id.au, lukas.bulwahn@gmail.com,
linux@roeck-us.net, nathanl@linux.ibm.com,
ye.xingchen@zte.com.cn, npiggin@gmail.com, nathan@kernel.org,
hbathini@linux.ibm.com, atrajeev@linux.vnet.ibm.com,
yuanjilin@cdjrlc.com, pali@kernel.org, farosas@linux.ibm.com,
geoff@infradead.org,
Linus Torvalds <torvalds@linux-foundation.org>,
gustavoars@kernel.org, lihuafei1@huawei.com,
zhengyongjun3@huawei.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [GIT PULL] Please pull powerpc/linux.git powerpc-6.1-1 tag
Date: Tue, 11 Oct 2022 11:00:15 +1100 [thread overview]
Message-ID: <d402a6a0a11d84906ecba3909f4c8f880298dc0f.camel@linux.ibm.com> (raw)
In-Reply-To: <Y0ScAhqysKK6Hrks@zx2c4.com>
On Mon, 2022-10-10 at 16:26 -0600, Jason A. Donenfeld wrote:
>
> Bisected:
>
> 7e92e01b724526b98cbc7f03dd4afa0295780d56 is the first bad commit
> commit 7e92e01b724526b98cbc7f03dd4afa0295780d56
> Author: Rohan McLure <rmclure@linux.ibm.com>
> Date: Wed Sep 21 16:56:01 2022 +1000
>
> powerpc: Provide syscall wrapper
>
> Implement syscall wrapper as per s390, x86, arm64. When enabled
> cause handlers to accept parameters from a stack frame rather
> than
> from user scratch register state. This allows for user registers
> to be
> safely cleared in order to reduce caller influence on speculation
> within syscall routine. The wrapper is a macro that emits syscall
> handler symbols that call into the target handler, obtaining its
> parameters from a struct pt_regs on the stack.
>
> As registers are already saved to the stack prior to calling
> system_call_exception, it appears that this function is executed
> more
> efficiently with the new stack-pointer convention than with
> parameters
> passed by registers, avoiding the allocation of a stack frame for
> this
> method. On a 32-bit system, we see >20% performance increases on
> the
> null_syscall microbenchmark, and on a Power 8 the performance
> gains
> amortise the cost of clearing and restoring registers which is
> implemented at the end of this series, seeing final result of
> ~5.6%
> performance improvement on null_syscall.
>
> Syscalls are wrapped in this fashion on all platforms except for
> the
> Cell processor as this commit does not provide SPU support. This
> can be
> quickly fixed in a successive patch, but requires
> spu_sys_callback to
> allocate a pt_regs structure to satisfy the wrapped calling
> convention.
>
> Co-developed-by: Andrew Donnellan <ajd@linux.ibm.com>
> Signed-off-by: Andrew Donnellan <ajd@linux.ibm.com>
> Signed-off-by: Rohan McLure <rmclure@linux.ibm.com>
> Reviewed-by: Nicholas Piggin <npiggin@gmai.com>
> [mpe: Make incompatible with COMPAT to retain clearing of high
> bits of args]
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> Link:
> https://lore.kernel.org/r/20220921065605.1051927-22-rmclure@linux.ibm.com
Thanks for bisecting, this is interesting! Could you provide your
.config and the environment you're running in? Your reproducer doesn't
seem to trigger it on my baremetal POWER8 pseries_le_defconfig.
--
Andrew Donnellan OzLabs, ADL Canberra
ajd@linux.ibm.com IBM Australia Limited
next prev parent reply other threads:[~2022-10-11 0:02 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 11:01 [GIT PULL] Please pull powerpc/linux.git powerpc-6.1-1 tag Michael Ellerman
2022-10-09 21:17 ` pr-tracker-bot
2022-10-10 19:25 ` Jason A. Donenfeld
2022-10-10 20:03 ` Jason A. Donenfeld
2022-10-10 22:26 ` Jason A. Donenfeld
2022-10-11 0:00 ` Andrew Donnellan [this message]
2022-10-11 0:13 ` Jason A. Donenfeld
2022-10-11 1:44 ` Michael Ellerman
2022-10-11 2:57 ` Jason A. Donenfeld
2022-10-11 9:34 ` Michael Ellerman
2022-10-11 1:53 ` Michael Ellerman
2022-10-11 2:57 ` Jason A. Donenfeld
2022-10-11 9:35 ` Michael Ellerman
2022-10-11 11:10 ` Nicholas Piggin
2022-10-12 14:18 ` Guenter Roeck
2022-10-12 15:49 ` Jason A. Donenfeld
2022-10-12 16:44 ` Guenter Roeck
2022-10-12 17:20 ` Jason A. Donenfeld
2022-10-12 17:48 ` Guenter Roeck
2022-10-12 18:37 ` Jason A. Donenfeld
2022-10-13 5:17 ` Nicholas Piggin
2022-10-12 22:16 ` Guenter Roeck
2022-10-13 0:03 ` Michael Ellerman
2022-10-13 0:21 ` Guenter Roeck
2022-10-13 5:03 ` Nicholas Piggin
2022-10-13 5:19 ` Jason A. Donenfeld
2022-10-13 5:20 ` Guenter Roeck
2022-10-13 5:22 ` Nicholas Piggin
2022-10-13 4:43 ` Guenter Roeck
2022-10-13 5:14 ` Nicholas Piggin
2022-10-13 18:55 ` Guenter Roeck
2022-10-12 16:45 ` Jason A. Donenfeld
2022-10-12 16:49 ` Guenter Roeck
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=d402a6a0a11d84906ecba3909f4c8f880298dc0f.camel@linux.ibm.com \
--to=ajd@linux.ibm.com \
--cc=Jason@zx2c4.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=cuigaosheng1@huawei.com \
--cc=david@redhat.com \
--cc=farosas@linux.ibm.com \
--cc=geoff@infradead.org \
--cc=gustavoars@kernel.org \
--cc=haren@linux.ibm.com \
--cc=hbathini@linux.ibm.com \
--cc=joel@jms.id.au \
--cc=lihuafei1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas.bulwahn@gmail.com \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=nathanl@linux.ibm.com \
--cc=nicholas@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=pali@kernel.org \
--cc=paul@paul-moore.com \
--cc=rmclure@linux.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=windhl@126.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=ye.xingchen@zte.com.cn \
--cc=yuanjilin@cdjrlc.com \
--cc=zhengyongjun3@huawei.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).