From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
arjan@linux.intel.com, karahmed@amazon.de, x86@kernel.org,
linux-kernel@vger.kernel.org, tim.c.chen@linux.intel.com,
bp@alien8.de, peterz@infradead.org, pbonzini@redhat.com,
ak@linux.intel.com, torvalds@linux-foundation.org,
gregkh@linux-foundation.org, dave.hansen@intel.com,
ashok.raj@intel.com, mingo@kernel.org
Subject: Re: [PATCH v4 6/7] x86/cpufeature: Blacklist SPEC_CTRL on early Spectre v2 microcodes
Date: Thu, 25 Jan 2018 16:16:14 +0000 [thread overview]
Message-ID: <20180125161547.33e63bb3@alans-desktop> (raw)
In-Reply-To: <1516887714.30244.121.camel@infradead.org>
> Here's what I have now. I'm happy enough with this, so the main thing
> I'm looking for is an ack from Alan for patch #5 of the series, if I've
> got that sufficiently correct now.
You have my ACK for patch 5: Any further changes I'll submit as updates
once it's merged.
I am happy with patch 5 and I think for 64bit we are probably done for
the mainstream. VIA/Centaur data would be nice.
The microcode otoh I don't think makes sense - do you want to be secure
with a slightly higher risk of crashes or insecure ? Once you can point
at a newer ucode for each case then yes I personally at least think it
then makes sense to tell users they want the newer one.
Alan
next prev parent reply other threads:[~2018-01-25 16:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 9:23 [PATCH v4 0/7] Basic Speculation Control feature support David Woodhouse
2018-01-25 9:23 ` [PATCH v4 1/7] x86/cpufeatures: Add CPUID_7_EDX CPUID leaf David Woodhouse
2018-01-25 9:23 ` [PATCH v4 2/7] x86/cpufeatures: Add Intel feature bits for Speculation Control David Woodhouse
2018-01-25 9:23 ` [PATCH v4 3/7] x86/cpufeatures: Add AMD " David Woodhouse
2018-01-25 9:23 ` [PATCH v4 4/7] x86/msr: Add definitions for new speculation control MSRs David Woodhouse
2018-01-25 9:23 ` [PATCH v4 5/7] x86/pti: Do not enable PTI on processors which are not vulnerable to Meltdown David Woodhouse
2018-01-25 9:42 ` Peter Zijlstra
2018-01-25 9:56 ` David Woodhouse
2018-01-25 10:01 ` Thomas Gleixner
2018-01-25 15:12 ` Alan Cox
2018-01-25 9:23 ` [PATCH v4 6/7] x86/cpufeature: Blacklist SPEC_CTRL on early Spectre v2 microcodes David Woodhouse
2018-01-25 10:43 ` David Woodhouse
2018-01-25 10:54 ` Thomas Gleixner
2018-01-25 11:20 ` David Woodhouse
2018-01-25 11:34 ` Thomas Gleixner
2018-01-25 13:41 ` David Woodhouse
2018-01-25 14:58 ` Thomas Gleixner
2018-01-25 16:16 ` Alan Cox [this message]
2018-01-25 16:24 ` Thomas Gleixner
2018-01-25 16:35 ` David Woodhouse
2018-01-26 9:40 ` Ingo Molnar
2018-01-25 9:23 ` [PATCH v4 7/7] x86/speculation: Add basic IBPB (Indirect Branch Prediction Barrier) support David Woodhouse
2018-01-25 11:41 ` Borislav Petkov
2018-01-25 11:47 ` David Woodhouse
2018-01-25 11:50 ` Borislav Petkov
2018-01-25 11:58 ` David Woodhouse
2018-01-25 12:03 ` Borislav Petkov
2018-01-25 12:11 ` David Woodhouse
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=20180125161547.33e63bb3@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dwmw2@infradead.org \
--cc=gregkh@linux-foundation.org \
--cc=karahmed@amazon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@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
all inboxes | Powered by JetHome®