historical-speck.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: Re: [PATCH v6 1/5] NX 1
Date: Tue, 15 Oct 2019 13:24:14 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1910151300360.1924@nanos.tec.linutronix.de> (raw)
In-Reply-To: <1570790416-25882-2-git-send-email-pbonzini@redhat.com>

On Fri, 11 Oct 2019, speck for Paolo Bonzini wrote:

This one and all other patches lack a

  From: ...
  Subject: ...
in the mail body, which requires manual fiddling with those patches when
applying them.

> Some processors may incur a machine check error possibly
> resulting in an unrecoverable cpu hang when an instruction fetch
> encounters a TLB multi-hit in the instruction TLB. This can occur
> when the page size is changed along with either the physical
> address or cache type [1].
> This issue affects both bare-metal x86 page tables and EPT.
> This can be mitigated by either eliminating the use of large
> pages or by using careful TLB invalidations when changing the
> page size in the page tables.
> Just like Spectre, Meltdown, L1TF and MDS, a new bit has been
> allocated in MSR_IA32_ARCH_CAPABILITIES (PSCHANGE_MC_NO) and will
> be set on CPUs which are mitigated against this issue.
> [1] For example please refer to erratum SKL002 in "6th Generation
> Intel Processor Family Specification Update"
> https://www.intel.com/content/www/us/en/products/docs/processors/core/desktop-6th-gen-core-family-spec-update.html
> https://www.google.com/search?q=site:intel.com+SKL002

Please don't provide links like this. They first one will be outdated in
the worst case before this goes public. The second one is giving the right
answer today, but does it so in 5 years from now?

I asked a gazillion times in the past to stick a copy of the errata PDF
into bugzilla.kernel.org and provide a link to the BZ entry. That has a
decent chance to be a permalink.

Sure, we don't want a public bugzilla entry for this right now, but we can
create a dummy entry and update the subject plus upload the file when the
stuff goes public.


is innocent enough for this.



  parent reply	other threads:[~2019-10-15 11:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 10:40 [MODERATED] [PATCH v6 0/5] NX 0 Paolo Bonzini
2019-10-11 10:40 ` [MODERATED] [PATCH v6 1/5] NX 1 Paolo Bonzini
2019-10-11 13:18   ` [MODERATED] " Konrad Rzeszutek Wilk
2019-10-15 11:24   ` Thomas Gleixner [this message]
2019-10-15 19:48     ` Paolo Bonzini
2019-10-23 16:18       ` Tyler Hicks
2019-10-11 10:40 ` [MODERATED] [PATCH v6 2/5] NX 2 Paolo Bonzini
2019-10-11 13:18   ` [MODERATED] " Konrad Rzeszutek Wilk
2019-10-15 19:37   ` Tyler Hicks
2019-10-11 10:40 ` [MODERATED] [PATCH v6 3/5] NX 3 Paolo Bonzini
2019-10-11 10:40 ` [MODERATED] [PATCH v6 4/5] NX 4 Paolo Bonzini
2019-10-11 10:40 ` [MODERATED] [PATCH v6 5/5] NX 5 Paolo Bonzini

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.21.1910151300360.1924@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=speck@linutronix.de \


* 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).