From: Tim Chen <tim.c.chen@linux.intel.com>
To: "Thomas Gleixner" <tglx@linutronix.de>, "Jörg Otte" <jrg.otte@gmail.com>
Cc: kirill.shutemov@linux.intel.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [v4.17-rcx] Lost IBPB, IBRS_FW support for spectre_v2 mitigation.
Date: Tue, 1 May 2018 16:07:36 -0700 [thread overview]
Message-ID: <380c0c14-fd7a-86e7-90a6-629df06da4ef@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1805012025460.1596@nanos.tec.linutronix.de>
On 05/01/2018 11:27 AM, Thomas Gleixner wrote:
> On Tue, 1 May 2018, Thomas Gleixner wrote:
>> On Tue, 1 May 2018, Jörg Otte wrote:
>>> 2018-04-30 21:53 GMT+02:00 Thomas Gleixner <tglx@linutronix.de>:
>>>> --- a/arch/x86/kernel/cpu/common.c
>>>> +++ b/arch/x86/kernel/cpu/common.c
>>>> @@ -848,6 +848,11 @@ void get_cpu_cap(struct cpuinfo_x86 *c)
>>>> c->x86_power = edx;
>>>> }
>>>>
>>>> + if (c->extended_cpuid_level >= 0x80000008) {
>>>> + cpuid(0x80000008, &eax, &ebx, &ecx, &edx);
>>>> + c->x86_capability[CPUID_8000_0008_EBX] = ebx;
>>>> + }
>>>> +
>>>> if (c->extended_cpuid_level >= 0x8000000a)
>>>> c->x86_capability[CPUID_8000_000A_EDX] = cpuid_edx(0x8000000a);
>>>>
>>>
>>> No, does not fix it.
>>
>> Then I really have no idea how reverting the patch you pointed out would
>> fix it.
>
> Can you please carefully recheck:
>
> 1) rc3 with d94a155c59c9 reverted.
I saw the same issue that Jorg Otte reported on a coffee lake system
with vanilla 4.17-rc3.
Reverting d94a155c59c9 did the trick for me.
Thanks.
Tim
>
> 2) rc3 with the above patch applied.
>
> If #1 works then #2 must work as well.
>
> Thanks,
>
> tglx
>
next prev parent reply other threads:[~2018-05-01 23:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 15:59 [v4.17-rcx] Lost IBPB, IBRS_FW support for spectre_v2 mitigation Jörg Otte
2018-04-30 19:53 ` Thomas Gleixner
2018-05-01 7:39 ` Jörg Otte
2018-05-01 12:59 ` Thomas Gleixner
2018-05-01 18:27 ` Thomas Gleixner
2018-05-01 23:07 ` Tim Chen [this message]
2018-05-01 20:14 ` Linus Torvalds
2018-05-02 7:43 ` Jörg Otte
2018-05-02 9:02 ` Thomas Gleixner
2018-05-02 9:25 ` Jörg Otte
2018-05-02 12:20 ` Thomas Gleixner
2018-05-04 16:18 ` Borislav Petkov
2018-05-05 9:47 ` Jörg Otte
2018-05-05 9:53 ` Borislav Petkov
2018-05-02 14:48 ` [tip:x86/urgent] x86/cpu: Restore CPUID_8000_0008_EBX reload tip-bot for Thomas Gleixner
2018-05-02 18:08 ` Tim Chen
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=380c0c14-fd7a-86e7-90a6-629df06da4ef@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=bp@alien8.de \
--cc=jrg.otte@gmail.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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