mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Boris Petkov <bp@suse.de>
To: Peter Zijlstra <peterz@infradead.org>,
	hpa@zytor.com, torvalds@linux-foundation.org, tglx@linutronix.de,
	mingo@kernel.org, Yazen.Ghannam@amd.com, mirh@protonmail.ch,
	sherry.hurwitz@amd.com, stable@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86/cpu/AMD: Apply the Erratum 688 fix when the BIOS doesn't
Date: Sun, 22 Oct 2017 16:01:38 +0200	[thread overview]
Message-ID: <A2B4E471-F8FD-4244-9AC4-D6D06A07FAA0@suse.de> (raw)
In-Reply-To: <20171022130429.GA3165@worktop.lehotels.local>

On October 22, 2017 3:04:29 PM GMT+02:00, Peter Zijlstra <peterz@infradead.org> wrote:
>I realize this is an erratum work around, but would it be too much to
>ask for a small comment explaining the magic values?

Revision guide doesn't state what those bits are. By the looks of it, they could be some sort of chicken bits turning off something.

>Except for all CPUs that were not online at this point in time... So
>suppose I boot with a limited number of CPUs and then later bring up
>the
>rest, bad things happen.

Well, those are small laptops and they're 1 or 2 CPUs tops and you really really really have to try to shoot yourself in the foot...


-- 
Sent from a small device: formatting sux and brevity is inevitable. 

      reply	other threads:[~2017-10-22 14:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-22 10:47 [PATCH] x86/AMD: Apply Erratum 688 fix when " Borislav Petkov
2017-10-22 11:04 ` Ingo Molnar
2017-10-22 11:12   ` Borislav Petkov
2017-10-22 12:14     ` Ingo Molnar
2017-10-22 12:16 ` [tip:x86/urgent] x86/cpu/AMD: Apply the Erratum 688 fix when the " tip-bot for Borislav Petkov
2017-10-22 13:04   ` Peter Zijlstra
2017-10-22 14:01     ` Boris Petkov [this message]

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=A2B4E471-F8FD-4244-9AC4-D6D06A07FAA0@suse.de \
    --to=bp@suse.de \
    --cc=Yazen.Ghannam@amd.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mirh@protonmail.ch \
    --cc=peterz@infradead.org \
    --cc=sherry.hurwitz@amd.com \
    --cc=stable@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

all inboxes | Powered by JetHome®