public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
	Joerg Roedel <joerg.roedel@amd.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] x86: mce init optimization and signedness fixup
Date: Thu, 11 Oct 2007 13:30:34 -0400	[thread overview]
Message-ID: <20071011173034.GB21339@redhat.com> (raw)
In-Reply-To: <alpine.LFD.0.9999.0710111844000.15917@localhost.localdomain>

On Thu, Oct 11, 2007 at 06:50:12PM +0200, Thomas Gleixner wrote:
 > On Thu, 11 Oct 2007, Christoph Egger wrote:
 > > On Thursday 11 October 2007 16:55:36 Thomas Gleixner wrote:
 > > > > > > +
 > > > > > > +	if (!cpu_has(c, X86_FEATURE_MCA) || !cpu_has(c, X86_FEATURE_MCE)) {
 > > > > > > +		printk(KERN_INFO "CPU%i: No machine check support available\n",
 > > > > > > +			smp_processor_id());
 > > > > > > +		return;
 > > > > >
 > > > > > This breaks winchip MCE support.
 > > > >
 > > > > First, what is a winchip? It sounds to be something windows specific. ;)
 > > > > Second, can you explain in which way MCE support gets broken, please?
 > > >
 > > > First, winchip is the code name of Centaurs early x86 cpus.
 > > >
 > > > Second, those beasts do not have FEATURE_MCA, but they have FEATURE_MCE,
 > > > so they support the fatal exception, but not the non fatal check.
 > > 
 > > So when I change the above code snippet to:
 > > 
 > > +	if (!cpu_has(c, X86_FEATURE_MCE)) {
 > > +		printk(KERN_INFO "CPU%i: No machine check support available\n",
 > > +			smp_processor_id());
 > > +		return;
 > > 
 > > Would this make the whole patch acceptable then?
 > 
 > Yeah, but then we can clean up the extra checks for _MCE in the various 
 > cpu type init functions as well.
 
I question the value of adding the printk.
It's not a failure, there's nothing the user can do about it,
and it adds no real value, just more noise to the dmesg.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2007-10-11 17:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11 12:17 [PATCH 0/2] x86: MCE optimization and cleanups Joerg Roedel
2007-10-11 12:17 ` [PATCH 1/2] x86: mce init optimization and signedness fixup Joerg Roedel
2007-10-11 13:51   ` Thomas Gleixner
2007-10-11 14:01     ` Christoph Egger
2007-10-11 14:55       ` Thomas Gleixner
2007-10-11 15:03         ` Christoph Egger
2007-10-11 16:50           ` Thomas Gleixner
2007-10-11 17:30             ` Dave Jones [this message]
2007-10-12  7:44             ` Christoph Egger
2007-10-11 19:55           ` Alan Cox
2007-10-11 15:11         ` Alan Cox
2007-10-11 12:17 ` [PATCH 2/2] x86: mce minor indent cleanup Joerg Roedel

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=20071011173034.GB21339@redhat.com \
    --to=davej@redhat.com \
    --cc=Christoph.Egger@amd.com \
    --cc=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@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