From: Michael Ellerman <mpe@ellerman.id.au>
To: LEROY Christophe <christophe.leroy@c-s.fr>,
Diana Madalina Craciun <diana.craciun@nxp.com>
Cc: oss@buserror.net, Bharat Bhushan <bharat.bhushan@nxp.com>,
linuxppc-dev@lists.ozlabs.org, Leo Li <leoyang.li@nxp.com>
Subject: Re: [PATCH v4 4/6] powerpc/fsl: Enable cpu vulnerabilities reporting for NXP PPC BOOK3E
Date: Thu, 19 Jul 2018 22:05:15 +1000 [thread overview]
Message-ID: <87601bctxg.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20180718180203.Horde.hNnOtk9Z-nuEx9HefV50JQ1@messagerie.si.c-s.fr>
LEROY Christophe <christophe.leroy@c-s.fr> writes:
> Diana Madalina Craciun <diana.craciun@nxp.com> a =C3=A9crit=C2=A0:
>> On 7/17/2018 7:47 PM, LEROY Christophe wrote:
>>> Diana Craciun <diana.craciun@nxp.com> a =C3=A9crit :
>>>> The NXP PPC Book3E platforms are not vulnerable to meltdown and
>>>> Spectre v4, so make them PPC_BOOK3S_64 specific.
>>>>
>>>> Signed-off-by: Diana Craciun <diana.craciun@nxp.com>
>>>> ---
>>>> History:
>>>>
>>>> v2-->v3
>>>> - used the existing functions for spectre v1/v2
>>>>
>>>> arch/powerpc/Kconfig | 7 ++++++-
>>>> arch/powerpc/kernel/security.c | 2 ++
>>>> 2 files changed, 8 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
>>>> index 9f2b75f..116c953 100644
>>>> --- a/arch/powerpc/Kconfig
>>>> +++ b/arch/powerpc/Kconfig
>>>> @@ -165,7 +165,7 @@ config PPC
>>>> select GENERIC_CLOCKEVENTS_BROADCAST if SMP
>>>> select GENERIC_CMOS_UPDATE
>>>> select GENERIC_CPU_AUTOPROBE
>>>> - select GENERIC_CPU_VULNERABILITIES if PPC_BOOK3S_64
>>>> + select GENERIC_CPU_VULNERABILITIES if PPC_NOSPEC
>>> I don't understand. You say this patch is to make something specific
>>> to book3s64 specific, and you are creating a new config param that
>>> make things less specific
>>>
>>> Christophe
>>
>> In order to enable the vulnerabilities reporting on NXP socs I need to
>> enable them for PPC_FSL_BOOK3E. So they will be enabled for both
>> PPC_FSL_BOOK3E and PPC_BOOK3S_64. This is the reason for adding the
>> Kconfig. However this will enable: spectre v1/v2 and meltdown. NXP socs
>> are not vulnerable to meltdown, so I made the meltdown reporting
>> PPC_BOOK3S_64 specific. I guess I can have the PPC_NOSPEC definition in
>> a separate patch to be more clear.
>
> Yes you can. Or keep it as a single patch and add the details you gave=20=
=20
> me in the patch description.
Yeah I think the patch is fine, but the change log is a bit short on detail.
If you just send me a new change log I can fold it in.
cheers
next prev parent reply other threads:[~2018-07-19 12:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 11:09 [PATCH v4 0/6] powerpc/fsl: Speculation barrier for NXP PowerPC Book3E Diana Craciun
2018-07-17 11:09 ` [PATCH v4 1/6] powerpc/fsl: Disable the speculation barrier from the command line Diana Craciun
2018-07-17 11:09 ` [PATCH v4 2/6] powerpc/fsl: Document nospectre_v1 kernel parameter Diana Craciun
2018-07-17 11:09 ` [PATCH v4 3/6] powerpc/fsl: Make stf barrier PPC_BOOK3S_64 specific Diana Craciun
2018-07-17 11:09 ` [PATCH v4 4/6] powerpc/fsl: Enable cpu vulnerabilities reporting for NXP PPC BOOK3E Diana Craciun
2018-07-17 16:46 ` LEROY Christophe
2018-07-18 14:29 ` Diana Madalina Craciun
2018-07-18 16:02 ` LEROY Christophe
2018-07-19 12:05 ` Michael Ellerman [this message]
2018-07-20 15:34 ` Diana Madalina Craciun
2018-07-17 11:09 ` [PATCH v4 5/6] powerpc/fsl: Add barrier_nospec implementation for NXP PowerPC Book3E Diana Craciun
2018-07-17 11:09 ` [PATCH v4 6/6] powerpc/fsl: Sanitize the syscall table for NXP PowerPC 32 bit platforms Diana Craciun
2018-07-17 16:43 ` [PATCH v4 0/6] powerpc/fsl: Speculation barrier for NXP PowerPC Book3E LEROY Christophe
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=87601bctxg.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=bharat.bhushan@nxp.com \
--cc=christophe.leroy@c-s.fr \
--cc=diana.craciun@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=oss@buserror.net \
/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