From: Michael Ellerman <mpe@ellerman•id.au>
To: Christophe Leroy <christophe.leroy@csgroup•eu>,
Alistair Popple <alistair@popple•id.au>,
linuxppc-dev@lists•ozlabs.org
Cc: aneesh.kumar@linux•ibm.com, mikey@neuling•org, npiggin@gmail•com
Subject: Re: [PATCH v3 4/7] powerpc/dt_cpu_ftrs: Set current thread fscr bits
Date: Wed, 09 Mar 2022 21:28:40 +1100 [thread overview]
Message-ID: <87lexjmnc7.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <4c76a361-09a6-3c91-4ee8-36e035437496@csgroup.eu>
Christophe Leroy <christophe.leroy@csgroup•eu> writes:
> Le 21/05/2020 à 03:43, Alistair Popple a écrit :
>> Setting the FSCR bit directly in the SPR only sets it during the initial
>> boot and early init of the kernel but not for the init process or any
>> subsequent kthreads. This is because the thread_struct for those is
>> copied from the current thread_struct setup at boot which doesn't
>> reflect any changes made to the FSCR during cpu feature detection. This
>> patch ensures the current thread state is updated to match once feature
>> detection is complete.
>>
>> Signed-off-by: Alistair Popple <alistair@popple•id.au>
>
> I see that the series has been merged but this patch was left over.
>
> Has it been forgotten or is it rejected ?
I fixed the underlying issue, see:
912c0a7f2b5d ("powerpc/64s: Save FSCR to init_task.thread.fscr after feature init")
So I guess it was superseeded (by a preceeding patch).
cheers
next prev parent reply other threads:[~2022-03-09 10:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 1:43 [PATCH v3 0/7] Base support for POWER10 Alistair Popple
2020-05-21 1:43 ` [PATCH v3 1/7] powerpc: Add new HWCAP bits Alistair Popple
2020-05-21 1:43 ` [PATCH v3 2/7] powerpc: Add support for ISA v3.1 Alistair Popple
2020-05-21 1:43 ` [PATCH v3 3/7] powerpc/dt_cpu_ftrs: Advertise support for ISA v3.1 if selected Alistair Popple
2020-05-21 1:43 ` [PATCH v3 4/7] powerpc/dt_cpu_ftrs: Set current thread fscr bits Alistair Popple
2022-03-09 8:25 ` Christophe Leroy
2022-03-09 10:28 ` Michael Ellerman [this message]
2020-05-21 1:43 ` [PATCH v3 5/7] powerpc/dt_cpu_ftrs: Enable Prefixed Instructions Alistair Popple
2020-05-21 1:43 ` [PATCH v3 6/7] powerpc/dt_cpu_ftrs: Add MMA feature Alistair Popple
2020-05-21 17:17 ` Paul A. Clarke
2020-05-21 1:43 ` [PATCH v3 7/7] powerpc: Add POWER10 architected mode Alistair Popple
2020-06-09 5:28 ` [PATCH v3 0/7] Base support for POWER10 Michael Ellerman
2020-06-09 16:51 ` Murilo Opsfelder Araújo
2020-06-10 5:30 ` Michael Ellerman
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=87lexjmnc7.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=alistair@popple$(echo .)id.au \
--cc=aneesh.kumar@linux$(echo .)ibm.com \
--cc=christophe.leroy@csgroup$(echo .)eu \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mikey@neuling$(echo .)org \
--cc=npiggin@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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