mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: Adrian Bunk <bunk@kernel.org>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
	"LKML (Cc removed)" <linux-kernel@vger.kernel.org>
Subject: Re: coding for optimizations (Re: [PATCH 1/2] i386: mce cleanup part1: functional change)
Date: Thu, 11 Oct 2007 18:13:50 +0200	[thread overview]
Message-ID: <20071011161350.GG22435@flower.upol.cz> (raw)
In-Reply-To: <20071011152129.GY16424@stusta.de>

On Thu, Oct 11, 2007 at 05:21:30PM +0200, Adrian Bunk wrote:
> On Thu, Oct 11, 2007 at 05:26:09PM +0200, Oleg Verych wrote:
> > On Thu, Oct 11, 2007 at 01:14:29AM +0200, Adrian Bunk wrote:
> > [] 
> > > It's also a quite ill idea to think about whether gcc might produce a 
> > > few bytes more or less code at the if when there's such a long printk() 
> > > in the middle...
> > 
> > printk() problem was discussed with proper banana userspace replacement
> > proposition by me, so i don't care much.
> > 
> > Though, why MCE can't be enabled/disabled by config option? Native
> > engineers from proper company should know what processors have this
> > feature... If kconfig isn't flexible for this, i'm glad to hear
> > opinions. If it's needed anyway, then sorry.
> 
> You should better say sorry for not having checked that it can already 
> be disabled with a kconfig option...

Talk is not about wana-build-MCE-in, given to the user's sake. But about
flexible selection of this code, if it is really supported by CPU, when
user have it enabled (see winchip/preventium sub-thread). More work, it
is not such quick patch, certainly, but this is needed for famous i386.

I wonder, why such patch wasn't introduced long time ago. Modern
(cheap) chips have no MCE?
____

  reply	other threads:[~2007-10-11 15:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-09 12:49 [PATCH 0/2] i386: MCE updates Joerg Roedel
2007-10-09 12:49 ` [PATCH 1/2] i386: mce cleanup part1: functional change Joerg Roedel
2007-10-09 16:04   ` Oleg Verych
2007-10-09 16:06     ` Joerg Roedel
2007-10-09 16:32       ` Oleg Verych
2007-10-09 16:54         ` Joerg Roedel
2007-10-09 20:46         ` Valdis.Kletnieks
2007-10-10  1:58           ` Oleg Verych
2007-10-09 17:33       ` coding for optimizations (Re: [PATCH 1/2] i386: mce cleanup part1: functional change) Oleg Verych
2007-10-09 18:30         ` Joerg Roedel
2007-10-10 23:14           ` Adrian Bunk
2007-10-11 15:26             ` Oleg Verych
2007-10-11 15:21               ` Adrian Bunk
2007-10-11 16:13                 ` Oleg Verych [this message]
2007-10-09 12:49 ` [PATCH 2/2] i386: mce cleanup part2: conding style cleanups 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=20071011161350.GG22435@flower.upol.cz \
    --to=olecom@flower.upol.cz \
    --cc=bunk@kernel.org \
    --cc=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.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®