From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: Re: [patch 0/2] x86/hotplug: Cure the MCE wreckage
Date: Mon, 2 Jul 2018 15:24:46 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1807021524320.1659@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20180702122743.GM2494@hirez.programming.kicks-ass.net>
On Mon, 2 Jul 2018, speck for Peter Zijlstra wrote:
> On Fri, Jun 29, 2018 at 04:05:46PM +0200, speck for Thomas Gleixner wrote:
> > As Dave pointed out, the HT siblings have to be booted up at least once in
> > order to set the CR4.MCE bit. Otherwise a MCE will cause the Internal
> > Processor Error to be raised which in turn causes shutdown or reset.
>
> Urghh.. but doesn't this also mean that things like nosmp/maxcpus= are
> currently broken?
Of course.
prev parent reply other threads:[~2018-07-02 13:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 14:05 [patch 0/2] x86/hotplug: Cure the MCE wreckage Thomas Gleixner
2018-06-29 14:05 ` [patch 1/2] Revert "x86/apic: Ignore secondary threads if nosmt=force" Thomas Gleixner
2018-06-29 14:05 ` [patch 2/2] cpu/hotplug: Boot HT siblings at least once Thomas Gleixner
2018-06-29 19:13 ` [MODERATED] " Josh Poimboeuf
2018-06-29 20:25 ` Josh Poimboeuf
2018-06-29 20:52 ` Josh Poimboeuf
2018-06-29 21:47 ` Thomas Gleixner
2018-06-29 19:17 ` [MODERATED] " Luck, Tony
2018-06-29 19:27 ` Thomas Gleixner
2018-06-29 20:57 ` [MODERATED] " Luck, Tony
2018-06-29 21:01 ` [MODERATED] " Borislav Petkov
2018-06-29 21:07 ` Luck, Tony
2018-06-29 21:48 ` Thomas Gleixner
2018-06-29 20:08 ` [MODERATED] " Josh Poimboeuf
2018-06-30 16:38 ` Borislav Petkov
2018-07-02 12:27 ` [MODERATED] Re: [patch 0/2] x86/hotplug: Cure the MCE wreckage Peter Zijlstra
2018-07-02 13:24 ` Thomas Gleixner [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=alpine.DEB.2.21.1807021524320.1659@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=speck@linutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).