From: Srinivas Ramana <sramana@codeaurora.org>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
will@kernel.org, catalin.marinas@arm.com, maz@kernel.org,
will.deacon@arm.com
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: Set SSBS for user threads while creation
Date: Tue, 24 Dec 2019 14:00:05 +0530 [thread overview]
Message-ID: <3a50c921-b37b-ea3d-1b9e-87113d3d3fd3@codeaurora.org> (raw)
In-Reply-To: <d490d6ce-8b07-ce79-4580-ac80f239312a@arm.com>
On 12/24/2019 12:36 PM, Anshuman Khandual wrote:
>
>
> On 12/23/2019 06:32 PM, Srinivas Ramana wrote:
>> Current SSBS implementation takes care of setting the
>> SSBS bit in start_thread() for user threads. While this works
>> for tasks launched with fork/clone followed by execve, for cases
>> where userspace would just call fork (eg, Java applications) this
>> leaves the SSBS bit unset. This results in performance
>> regression for such tasks.
>>
>> It is understood that commit cbdf8a189a66 ("arm64: Force SSBS
>> on context switch") masks this issue, but that was done for a
>> different reason where heterogeneous CPUs(both SSBS supported
>> and unsupported) are present. It is appropriate to take care
>> of the SSBS bit for all threads while creation itself.
>
> So this fixes the situation (i.e low performance) from the creation time
> of a task with fork() which will never see a subsequent execve, till it
> gets context switched for the very first time ?
>
Yes, that is correct.
>>
>> Fixes: 8f04e8e6e29c ("arm64: ssbd: Add support for PSTATE.SSBS rather than trapping to EL3")
>> Signed-off-by: Srinivas Ramana <sramana@codeaurora.org>
>> ---
>> arch/arm64/kernel/process.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c
>> index 71f788cd2b18..a8f05cc39261 100644
>> --- a/arch/arm64/kernel/process.c
>> +++ b/arch/arm64/kernel/process.c
>> @@ -399,6 +399,13 @@ int copy_thread(unsigned long clone_flags, unsigned long stack_start,
>> */
>> if (clone_flags & CLONE_SETTLS)
>> p->thread.uw.tp_value = childregs->regs[3];
>> +
>> + if (arm64_get_ssbd_state() != ARM64_SSBD_FORCE_ENABLE) {
>> + if (is_compat_thread(task_thread_info(p)))
>> + set_compat_ssbs_bit(childregs);
>> + else
>> + set_ssbs_bit(childregs);
>> + }
>> } else {
>> memset(childregs, 0, sizeof(struct pt_regs));
>> childregs->pstate = PSR_MODE_EL1h;
>>
Thanks,
-- Srinivas R
--
Qualcomm India Private Limited, on behalf of Qualcomm Innovation
Center, Inc., is a member of Code Aurora Forum, a Linux Foundation
Collaborative Project
next prev parent reply other threads:[~2019-12-24 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 13:02 [PATCH] arm64: Set SSBS for user threads while creation Srinivas Ramana
2019-12-24 7:06 ` Anshuman Khandual
2019-12-24 8:30 ` Srinivas Ramana [this message]
2020-01-02 18:01 ` Catalin Marinas
2020-01-09 15:17 ` Will Deacon
2020-01-29 11:48 ` Srinivas Ramana
2020-01-29 16:13 ` Will Deacon
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=3a50c921-b37b-ea3d-1b9e-87113d3d3fd3@codeaurora.org \
--to=sramana@codeaurora.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=will.deacon@arm.com \
--cc=will@kernel.org \
/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