* intel CPU vulnerability NO_SSB whitelist for AIRMONT @ 2024-07-09 7:51 Shanavas.K.S 2024-07-10 6:15 ` Pawan Gupta 0 siblings, 1 reply; 3+ messages in thread From: Shanavas.K.S @ 2024-07-09 7:51 UTC (permalink / raw) To: linux-kernel Hi All, This is in reference to https://github.com/torvalds/linux/blame/master/arch/x86/kernel/cpu/common.c#L1169. The whitelist for INTEL_ATOM_AIRMONT has NO_SSB enabled which means cache speculation vulnerability(spectre 4,CVE-2018-3639) is not applicable to this processor. But NO_SSB is not set for INTEL_ATOM_AIRMONT_NP and INTEL_ATOM_AIRMONT_MID. Are these settings missing for AIRMONT_NP and AIRMONT_MID or is there a real difference between cache speculation between these processors? regards Shanavas ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: intel CPU vulnerability NO_SSB whitelist for AIRMONT 2024-07-09 7:51 intel CPU vulnerability NO_SSB whitelist for AIRMONT Shanavas.K.S @ 2024-07-10 6:15 ` Pawan Gupta 0 siblings, 0 replies; 3+ messages in thread From: Pawan Gupta @ 2024-07-10 6:15 UTC (permalink / raw) To: Shanavas.K.S; +Cc: linux-kernel On Tue, Jul 09, 2024 at 01:21:44PM +0530, Shanavas.K.S wrote: > Hi All, > This is in reference to > https://github.com/torvalds/linux/blame/master/arch/x86/kernel/cpu/common.c#L1169. > The whitelist for INTEL_ATOM_AIRMONT has NO_SSB enabled which means > cache speculation vulnerability(spectre 4,CVE-2018-3639) is not > applicable to this processor. But NO_SSB is not set for > INTEL_ATOM_AIRMONT_NP and INTEL_ATOM_AIRMONT_MID. Are these settings > missing for AIRMONT_NP and AIRMONT_MID or is there a real difference > between cache speculation between these processors? I believe they were released much later than AIRMONT and hence should be enumerating MSR IA32_ARCH_CAPABILITIES[SSB_NO](bit 4). If you have these system, is bit 4 not set? If it is set there is no need to explicitly add NO_SSB to the table. ^ permalink raw reply [flat|nested] 3+ messages in thread
[parent not found: <CAEJ9NQdJwwpYmGmqm9BESViBDH9P=QQJVZfnO12BTESEKYRFjg@mail.gmail.com>]
[parent not found: <20240807190217.f4ex7xlzb4wpxxnl@desk>]
[parent not found: <CAEJ9NQcYU6dRZJM818Ae3f-H86BKo=iaya7jbt3BH+G1O1gsQQ@mail.gmail.com>]
* Re: intel CPU vulnerability NO_SSB whitelist for AIRMONT [not found] ` <CAEJ9NQcYU6dRZJM818Ae3f-H86BKo=iaya7jbt3BH+G1O1gsQQ@mail.gmail.com> @ 2024-08-28 11:12 ` Shanavas.K.S 0 siblings, 0 replies; 3+ messages in thread From: Shanavas.K.S @ 2024-08-28 11:12 UTC (permalink / raw) To: Pawan Gupta, linux-kernel Thanks for the response. Please create the patch from your side Regards Shanavas > On Thu, Aug 8, 2024 at 12:32 AM Pawan Gupta > <pawan.kumar.gupta@linux.intel.com> wrote: > > > > On Wed, Aug 07, 2024 at 12:57:47PM +0530, Shanavas.K.S wrote: > > > Hi Pawan Gupta > > > Thanks for the comment. I have checked IA32_ARCH_CAPABILITIES > > > register but it is resulting in "unchecked MSR access error: RDMSR > > > from 0x10a at rIP: 0xffffffff8286cc26". I am assuming the reason is > > > the MSR register is not available in our processor. > > > > Thats what it looks like. > > > > > Does it mean that NO_SSB should be added to the whitelist for > > > INTEL_ATOM_AIRMONT_NP and INTEL_ATOM_AIRMONT_MID if these processors are > > > not susceptible to cache speculation vulnerability? > > > > Correct, NO_SSB should be added to the whitelist for AIRMONT variants. Let > > me know if you are planning to submit a patch for this. Otherwise, I will. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-08-28 11:12 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-07-09 7:51 intel CPU vulnerability NO_SSB whitelist for AIRMONT Shanavas.K.S
2024-07-10 6:15 ` Pawan Gupta
[not found] <CAEJ9NQdJwwpYmGmqm9BESViBDH9P=QQJVZfnO12BTESEKYRFjg@mail.gmail.com>
[not found] ` <20240807190217.f4ex7xlzb4wpxxnl@desk>
[not found] ` <CAEJ9NQcYU6dRZJM818Ae3f-H86BKo=iaya7jbt3BH+G1O1gsQQ@mail.gmail.com>
2024-08-28 11:12 ` Shanavas.K.S
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®