mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Andi Kleen <ak@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Fix thermal throttling reporting after kexec
Date: Sun, 11 Oct 2015 21:37:40 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1510112134191.6097@nanos> (raw)
In-Reply-To: <alpine.DEB.2.11.1510022233110.4500@nanos>

Andi,

On Fri, 2 Oct 2015, Thomas Gleixner wrote:
> On Thu, 1 Oct 2015, Andi Kleen wrote:
> > On Thu, Oct 01, 2015 at 11:50:00PM +0200, Andi Kleen wrote:
> > > > I see it under the correctness aspect. Mop up before you shut down.
> > > 
> > > Ok. I suspect if you want to clean up all registers there's much more
> > > to do.
> > > 
> > > BTW there's a small danger in it: if we ever crash accessing on
> > > of those registers panic may end up looping.
> > 
> > I thought more about it. Since this is per logical CPU state
> > the cleanup cannot be done in a normal shutdown callback (which
> > only runs on one CPU), but needs some kind of global IPI/NMI.
> > 
> > IPI could deadlock, so it would need to be NMI.
> > 
> > KVM already has one, but would need to re-organize that into
> > first into a generic callback infrastructure.
> > 
> > I don't think so much change is worth it for this one
> > somewhat dubious case. NMI code is also tricky and it's
> > probably better to keep the shut down paths as simple
> > and reliable as possible. Do you agree?
> 
> Yes. Makes sense.
> 
> Thanks for analysing it.

I wanted to pick this up, but then I noticed that it actually belongs
to X86 MCE INFRASTRUCTURE which is maintained by Tony and Borislav.

Can you please resend to them? It would be nice if you could add the
discussion about not cleaning it up in the changelog.

Thanks and sorry for noticing so late,

       tglx

  reply	other threads:[~2015-10-11 19:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 20:10 Andi Kleen
2015-10-01 12:15 ` Thomas Gleixner
2015-10-01 17:27   ` Andi Kleen
2015-10-01 21:41     ` Thomas Gleixner
2015-10-01 21:50       ` Andi Kleen
2015-10-01 22:04         ` Andi Kleen
2015-10-02 20:33           ` Thomas Gleixner
2015-10-11 19:37             ` Thomas Gleixner [this message]
2015-10-12 20:32 Andi Kleen
2015-10-12 20:33 ` Thomas Gleixner
2015-10-13 10:43   ` Borislav Petkov

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.11.1510112134191.6097@nanos \
    --to=tglx@linutronix.de \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®