From: Marc Zyngier <marc.zyngier@arm.com>
To: Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, will.deacon@arm.com,
catalin.marinas@arm.com
Subject: Re: [PATCHv2 11/19] arm64: don't reload GPRs after apply_ssbd
Date: Fri, 1 Jun 2018 15:41:30 +0100 [thread overview]
Message-ID: <57f6f0ca-8256-d642-fd59-034b989dc5c8@arm.com> (raw)
In-Reply-To: <20180601112441.37810-12-mark.rutland@arm.com>
On 01/06/18 12:24, Mark Rutland wrote:
> Now that all of the syscall logic works on the saved pt_regs, apply_ssbd
> can safely corrupt x0-x3 in the entry paths, and we no longer need to
> restore them. So let's remotve the logic doing so.
remove*
>
> With that logic gone, we can fold the branch target into the macro, so
> that callers need not deal with this. GAS provides \@, which provides a
> unique value per macro invocation, which we can use to create a unique
> label.
>
> Signed-off-by: Mark Rutland <mark.rutland@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Marc Zyngier <marc.zyngier@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
Acked-by: Marc Zyngier <marc.zyngier@arm.com>
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2018-06-01 14:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-01 11:24 [PATCHv2 00/19] arm64: invoke syscalls with pt_regs Mark Rutland
2018-06-01 11:24 ` [PATCHv2 01/19] arm64: consistently use unsigned long for thread flags Mark Rutland
2018-06-01 11:24 ` [PATCHv2 02/19] arm64: move SCTLR_EL{1,2} assertions to <asm/sysreg.h> Mark Rutland
2018-06-14 16:44 ` Will Deacon
2018-06-01 11:24 ` [PATCHv2 03/19] arm64: introduce sysreg_clear_set() Mark Rutland
2018-06-01 11:24 ` [PATCHv2 04/19] arm64: kill config_sctlr_el1() Mark Rutland
2018-06-01 11:24 ` [PATCHv2 05/19] arm64: kill change_cpacr() Mark Rutland
2018-06-01 11:24 ` [PATCHv2 06/19] arm64: move sve_user_{enable,disable} to <asm/fpsimd.h> Mark Rutland
2018-06-01 11:24 ` [PATCHv2 07/19] arm64: remove sigreturn wrappers Mark Rutland
2018-06-01 11:24 ` [PATCHv2 08/19] arm64: convert raw syscall invocation to C Mark Rutland
2018-06-01 11:24 ` [PATCHv2 09/19] arm64: convert syscall trace logic " Mark Rutland
2018-06-01 11:24 ` [PATCHv2 10/19] arm64: convert native/compat syscall entry " Mark Rutland
2018-06-01 11:24 ` [PATCHv2 11/19] arm64: don't reload GPRs after apply_ssbd Mark Rutland
2018-06-01 14:41 ` Marc Zyngier [this message]
2018-06-01 11:24 ` [PATCHv2 12/19] arm64: zero GPRs upon entry from EL0 Mark Rutland
2018-06-01 11:24 ` [PATCHv2 13/19] kernel: add ksys_personality() Mark Rutland
2018-06-01 11:24 ` [PATCHv2 14/19] kernel: add kcompat_sys_{f,}statfs64() Mark Rutland
2018-06-01 11:24 ` [PATCHv2 15/19] arm64: remove in-kernel call to sys_personality() Mark Rutland
2018-06-01 11:24 ` [PATCHv2 16/19] arm64: use {COMPAT,}SYSCALL_DEFINE0 for sigreturn Mark Rutland
2018-06-01 11:24 ` [PATCHv2 17/19] arm64: use SYSCALL_DEFINE6() for mmap Mark Rutland
2018-06-01 11:24 ` [PATCHv2 18/19] arm64: convert compat wrappers to C Mark Rutland
2018-06-01 11:24 ` [PATCHv2 19/19] arm64: implement syscall wrappers Mark Rutland
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=57f6f0ca-8256-d642-fd59-034b989dc5c8@arm.com \
--to=marc.zyngier@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®