From: Jonathan Corbet <corbet@lwn.net>
To: Tim Chen <tim.c.chen@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jiri Kosina <jikos@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Tom Lendacky <thomas.lendacky@amd.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Andrea Arcangeli <aarcange@redhat.com>,
David Woodhouse <dwmw@amazon.co.uk>,
Andi Kleen <ak@linux.intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Asit Mallick <asit.k.mallick@intel.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Jon Masters <jcm@redhat.com>, Waiman Long <longman9394@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>,
Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, x86@kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] x86/speculation: Add document to describe Spectre and its mitigations
Date: Fri, 28 Dec 2018 10:34:37 -0700 [thread overview]
Message-ID: <20181228103437.4c03c181@lwn.net> (raw)
In-Reply-To: <64efec3fda40c0758601bf9b1480a35d76d3c487.1545413988.git.tim.c.chen@linux.intel.com>
On Fri, 21 Dec 2018 09:44:44 -0800
Tim Chen <tim.c.chen@linux.intel.com> wrote:
> Andi and I have made an update to our draft of the Spectre admin guide.
> We may be out on Christmas vacation for a while. But we want to
> send it out for everyone to take a look.
>
> Thanks.
>
> Tim
>
> From: Andi Kleen <ak@linux.intel.com>
>
> There are no document in admin guides describing
> Spectre v1 and v2 side channels and their mitigations
> in Linux.
>
> Create a document to describe Spectre and the mitigation
> methods used in the kernel.
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> Signed-off-by: Tim Chen <tim.c.chen@linux.intel.com>
> ---
> Documentation/admin-guide/spectre.rst | 502 ++++++++++++++++++++++++++++++++++
> 1 file changed, 502 insertions(+)
> create mode 100644 Documentation/admin-guide/spectre.rst
I only saw this now, seems I wasn't copied... I'll take a deeper look, but
I have a couple of meta comments:
- This could arguably go in the security book rather than the admin
guide. I don't really have a strong opinion on which is right at the
moment, but others might.
- Wherever it ends up, can you also please add it to the appropriate
index.rst file so it actually gets built with the rest of the docs?
Thanks,
jon
next prev parent reply other threads:[~2018-12-28 17:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 17:44 [PATCH] x86/speculation: Add document to describe Spectre and its mitigations Tim Chen
2018-12-21 21:59 ` Ben Greear
2018-12-22 1:17 ` Tim Chen
2018-12-31 16:22 ` Ben Greear
2018-12-31 17:10 ` Arjan van de Ven
2019-01-07 17:57 ` Tim Chen
2019-01-09 0:58 ` Ben Greear
2019-01-09 1:35 ` Tim Chen
2018-12-23 23:11 ` Alexei Starovoitov
2019-01-08 21:12 ` Tim Chen
2019-01-09 1:11 ` Alexei Starovoitov
2019-01-09 1:41 ` Tim Chen
2019-01-09 2:42 ` Alexei Starovoitov
2018-12-28 17:34 ` Jonathan Corbet [this message]
2019-01-08 21:18 ` Tim Chen
2019-01-13 23:10 ` Pavel Machek
2019-01-13 23:12 ` Jiri Kosina
2019-01-14 12:01 ` Pavel Machek
2019-01-14 12:06 ` Jiri Kosina
2019-01-14 13:01 ` Pavel Machek
2019-01-14 13:06 ` Jiri Kosina
2019-01-14 14:39 ` Arjan van de Ven
2019-01-30 0:12 ` Thomas Gleixner
2019-02-12 12:00 ` Thomas Gleixner
2019-02-12 17:36 ` 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=20181228103437.4c03c181@lwn.net \
--to=corbet@lwn.net \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=asit.k.mallick@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jcm@redhat.com \
--cc=jikos@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman9394@gmail.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.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).