public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Mannthey <kmannth@us.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: lkml <linux-kernel@vger.kernel.org>, John Stultz <johnstul@us.ibm.com>
Subject: Re: [RFC][Patch] IBM Real-Time "SMI Free" mode drive -v2
Date: Wed, 16 Dec 2009 17:50:55 -0800	[thread overview]
Message-ID: <1261014655.6521.84.camel@keith-laptop> (raw)
In-Reply-To: <1261004964.21028.521.camel@laptop>

On Thu, 2009-12-17 at 00:09 +0100, Peter Zijlstra wrote:
> On Tue, 2009-12-15 at 12:09 -0800, Keith Mannthey wrote:
> > This driver supports the Real-Time Linux (RTL) BIOS feature.  The RTL
> > feature allows non-fatal System Management Interrupts (SMIs) to be
> > disabled on supported IBM platforms. 
> > 
> > 
> > The Device is presented as a special "_rtl_" table to the OS in the
> > Extended BIOS Data Area.  There is a simple protocol for entering and
> > exiting the mode at runtime.  This driver creates a simple sysfs
> > interface to allow a simple entry and exit from RTL mode in the
> > UFI/BIOS. 
> 
> Why not simply always run with these non-fatal SMIs disabled and provide
> their function through the OS proper?
> 
> That way you don't need no silly switches and gain consistent platform
> behaviour.

Peter, 

This driver will load and work on widely used Intel and AMD based IBM
hardware.  A decent amount of the IBM blades and a few of the rack-mount
servers with regular firmware support this mode.  This is not special
hardware with special features is is regular hardware/firmware that can
enter this special mode.

There are 2 major things that change when you in this mode that keep it
from being a good fit for many situations. 

1. ECC memory error detection and reporting is the sole responsibility
of the OS. I have practical experience with this and let just say this
does not "just work" everywhere even within Linux. 

2. The cpu can no longer be externally throttled. This means externally
implemented cooling or power saving options just don't work. 

These 2 things make it impractical for it to be an all the time
everywhere type of thing.  I think a run time state change the OS can
request is a good fit for the issues and complications at hand.

Thanks,
  Keith Mannthey 
  LTC Real-Time 


      parent reply	other threads:[~2009-12-17  1:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-15 20:09 [RFC][Patch] IBM Real-Time "SMI Free" mode drive -v2 Keith Mannthey
2009-12-15 23:12 ` Randy Dunlap
2009-12-15 23:58   ` Keith Mannthey
2009-12-15 23:49 ` Jonathan Corbet
2009-12-16  0:09   ` Thomas Gleixner
2009-12-16  0:38   ` Keith Mannthey
2009-12-16  0:50     ` Jonathan Corbet
2009-12-16  0:02 ` Alan Cox
2009-12-17  2:09   ` Keith Mannthey
2009-12-16 23:09 ` Peter Zijlstra
2009-12-17  1:37   ` john stultz
2009-12-17  2:06     ` Keith Mannthey
2009-12-17  1:50   ` Keith Mannthey [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=1261014655.6521.84.camel@keith-laptop \
    --to=kmannth@us.ibm.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.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