From: Dave Hansen <dave.hansen@intel.com>
To: David Woodhouse <dwmw@amazon.co.uk>,
arjan@linux.intel.com, tglx@linutronix.de, 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,
thomas.lendacky@amd.com
Subject: Re: [PATCH v2 4/5] x86/msr: Add definitions for new speculation control MSRs
Date: Tue, 23 Jan 2018 10:27:24 -0800 [thread overview]
Message-ID: <18ca2a5a-17df-e889-9c11-f5ee4c46de53@intel.com> (raw)
In-Reply-To: <1516726375-25168-5-git-send-email-dwmw@amazon.co.uk>
On 01/23/2018 08:52 AM, David Woodhouse wrote:
> +#define MSR_IA32_ARCH_CAPABILITIES 0x0000010a
> +#define ARCH_CAP_RDCL_NO (1 << 0) /* Not susceptible to Meltdown */
> +#define ARCH_CAP_IBRS_ALL (1 << 1) /* Enhanced IBRS support */
Do we want to spell out the silly Intel acronym? I don't know how we
fit it on the right side, but I do think we need to do it _somewhere_.
We need the code to stand on its own to some degree and not subject the
masses to reading the spec to understand the code.
/* Not to susceptible Rogue Data Cache Load aka Meltdown: */
#define ARCH_CAP_RDCL_NO (1 << 0)
next prev parent reply other threads:[~2018-01-23 18:27 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 16:52 [PATCH v2 0/5] Basic Speculation Control feature support David Woodhouse
2018-01-23 16:52 ` [PATCH v2 1/5] x86/cpufeatures: Add CPUID_7_EDX CPUID leaf David Woodhouse
2018-01-23 16:52 ` [PATCH v2 2/5] x86/cpufeatures: Add Intel feature bits for Speculation Control David Woodhouse
2018-01-23 18:43 ` Dave Hansen
2018-01-24 1:23 ` Woodhouse, David
2018-01-24 1:28 ` Dave Hansen
2018-01-24 8:13 ` Woodhouse, David
2018-01-23 16:52 ` [PATCH v2 3/5] x86/cpufeatures: Add AMD " David Woodhouse
2018-01-24 8:39 ` Kirill A. Shutemov
2018-01-24 8:40 ` David Woodhouse
2018-01-23 16:52 ` [PATCH v2 4/5] x86/msr: Add definitions for new speculation control MSRs David Woodhouse
2018-01-23 18:27 ` Dave Hansen [this message]
2018-01-23 18:31 ` Greg KH
2018-01-23 18:48 ` Woodhouse, David
2018-01-23 16:52 ` [PATCH v2 5/5] x86/pti: Do not enable PTI on fixed Intel processors David Woodhouse
2018-01-23 18:12 ` Andi Kleen
2018-01-24 1:21 ` David Woodhouse
2018-01-23 18:40 ` Dave Hansen
2018-01-24 1:27 ` David Woodhouse
2018-01-23 18:41 ` Dave Hansen
2018-01-23 18:44 ` Woodhouse, David
2018-01-23 18:45 ` Alan Cox
2018-01-23 19:02 ` Andrew Cooper
2018-01-23 20:45 ` Alan Cox
2018-01-23 20:38 ` Linus Torvalds
2018-01-23 20:50 ` David Woodhouse
2018-01-24 16:25 ` David Woodhouse
2018-01-24 17:07 ` Alan Cox
2018-01-24 17:42 ` David Woodhouse
2018-01-24 18:40 ` Alan Cox
2018-01-24 18:59 ` David Woodhouse
2018-01-24 19:37 ` 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=18ca2a5a-17df-e889-9c11-f5ee4c46de53@intel.com \
--to=dave.hansen@intel.com \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linux-foundation.org \
--cc=karahmed@amazon.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--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;
as well as URLs for NNTP newsgroup(s).