From: Juergen Gross <jgross@suse.com>
To: Borislav Petkov <bp@suse.de>
Cc: Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: lapic_suspend/lapic_resume wrong?
Date: Mon, 23 Nov 2015 10:57:43 +0100 [thread overview]
Message-ID: <5652E317.1000100@suse.com> (raw)
In-Reply-To: <20151123095018.GB5166@pd.tnic>
On 23/11/15 10:50, Borislav Petkov wrote:
> On Mon, Nov 23, 2015 at 10:32:35AM +0100, Juergen Gross wrote:
>> I don't know. I was more concerned what might happen in a kernel
>> configured with CONFIG_X86_MCE_INTEL but not CONFIG_X86_THERMAL_VECTOR.
>
> How can you even do that without patching Kconfig?
I didn't check it. You are right, can't happen (today).
The code is wrong nevertheless.
Juergen
next prev parent reply other threads:[~2015-11-23 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 7:46 lapic_suspend/lapic_resume wrong? Juergen Gross
2015-11-23 8:01 ` Ingo Molnar
2015-11-23 9:32 ` Juergen Gross
2015-11-23 9:50 ` Borislav Petkov
2015-11-23 9:57 ` Juergen Gross [this message]
2015-11-24 4:16 ` kbuild test robot
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=5652E317.1000100@suse.com \
--to=jgross@suse.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
--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