From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: Johannes Stezenbach <js@sig21.net>,
x86@kernel.org, linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: *PING* [PATCH]: x86: mce: fix mce warning with disabled lapic
Date: Wed, 12 Aug 2009 13:59:20 +0200 [thread overview]
Message-ID: <20090812115920.GA24215@elte.hu> (raw)
In-Reply-To: <87k51cgdt8.fsf@basil.nowhere.org>
* Andi Kleen <andi@firstfloor.org> wrote:
> *PING* can someone please take the patch in there and process the
> other suggestions?
Firstly, a basic patch submission technical matter: could you please
stop spamming maintainers of the x86/MCE code with such '*PING*'
private mails, for patches you never properly submitted to begin
with?
The proper way to submit an upstream kernel fix, as you should well
be aware of, is to send a patch with a proper title and to Cc: it to
lkml and the maintainers affected. You never did that, you only
posted a for-testing patch into a discussion. Please stop this
self-important posturing, it's somewhat annoying.
Also, another, patch log quality issue, please credit Johannes
properly. You put this into the changelog:
> Originally reported by Johannes Stezenbach
>
> This is a 2.6.31 candidate because it fixes a regression.
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
The proper way is to put this into the changelog:
Reported-by: Johannes Stezenbach <js@sig21.net>
And given that Johannes also tested the patch, another line of:
Tested-by: Johannes Stezenbach <js@sig21.net>
Would be appropriate as well.
Thirdly, we can do better with the fix itself too:
> +++ linux/arch/x86/kernel/cpu/mcheck/therm_throt.c
> @@ -236,6 +236,9 @@ void intel_init_thermal(struct cpuinfo_x
> int tm2 = 0;
> u32 l, h;
>
> + if (!cpu_has_apic || disable_apic)
> + return;
> +
> /* Thermal monitoring depends on ACPI and clock modulation*/
> if (!cpu_has(c, X86_FEATURE_ACPI) || !cpu_has(c, X86_FEATURE_ACC))
> return;
we already have that X86_FEATURE_ACPI and X86_FEATURE_ACC check and
a return statement. Would be better to expand that with the APIC
checks. Plus update the comment to also mention APIC as a
requirement plus fix the small error in the comment too while at it.
If these problems are fixed i'll apply the fix to tip:x86/urgent.
Thanks,
Ingo
prev parent reply other threads:[~2009-08-12 11:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 17:09 2.6.31-rc5 regression: x86 MCE malfunction on Thinkpad T42p Johannes Stezenbach
2009-08-09 10:03 ` Johannes Stezenbach
2009-08-09 10:34 ` Bartlomiej Zolnierkiewicz
2009-08-09 16:47 ` Johannes Stezenbach
2009-08-10 10:31 ` Andi Kleen
2009-08-10 12:27 ` Johannes Stezenbach
2009-08-10 12:32 ` Andi Kleen
2009-08-10 12:56 ` Johannes Stezenbach
2009-08-10 13:29 ` Ingo Molnar
2009-08-10 19:26 ` Johannes Stezenbach
2009-08-10 19:44 ` Andi Kleen
2009-08-10 20:05 ` Robert Richter
2009-08-10 20:14 ` Ingo Molnar
2009-08-10 20:37 ` Johannes Stezenbach
2009-08-10 21:31 ` Ingo Molnar
2009-08-10 22:13 ` Johannes Stezenbach
2009-08-11 9:34 ` [patch] cache-miss and cache-refs events on P6-mobile CPUs Ingo Molnar
2009-08-11 9:39 ` Peter Zijlstra
2009-08-11 11:06 ` Ingo Molnar
2009-08-11 11:21 ` Peter Zijlstra
2009-08-11 15:50 ` Johannes Stezenbach
2009-08-11 16:56 ` Ingo Molnar
2009-08-11 15:40 ` 2.6.31-rc5 regression: x86 MCE malfunction on Thinkpad T42p Johannes Stezenbach
2009-08-17 14:49 ` Steven Rostedt
2009-08-12 11:59 ` Ingo Molnar [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=20090812115920.GA24215@elte.hu \
--to=mingo@elte.hu \
--cc=andi@firstfloor.org \
--cc=js@sig21.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--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