mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Russ Anderson <rja@sgi.com>
Cc: Matthew Garrett <matthew.garrett@nebula.com>,
	minyard@acm.org, lenb@kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] Change ACPI IPMI support to "default y"
Date: Fri, 21 Feb 2014 01:10:21 +0100	[thread overview]
Message-ID: <1473995.mOCKVf8skD@vostro.rjw.lan> (raw)
In-Reply-To: <20140220201458.GA7099@sgi.com>

On Thursday, February 20, 2014 02:14:58 PM Russ Anderson wrote:
> On Tue, Feb 18, 2014 at 11:28:29AM -0500, Matthew Garrett wrote:
> > The ACPI IPMI driver implements IPMI operation region support for the ACPI
> > core. Systems that declare ACPI operation regions may reference them at any
> > time, including during kernel initialisation. These accesses will fail
> > unless the ACPI IPMI driver is present, and undesirable system behaviour
> > may result. Set the default to Y in order to encourage distributions and
> > users to configure kernels to avoid awkward surprises.
> 
> No, please do not build the ipmi_si driver into the kernel.
> Not all systems want, or need, the ipmi_si driver.  
> 
> The distro that added this change created all sorts of support
> problems.

Which distro was that?

Do you have any pointers to specific bug reports related to that?

Rafael


> Problems include kipmi0 spinning at 100% of cpu
> (creating a performance hit) and long boot delays (as the
> kernel tries to talk to a BMC that will never respond).
> It has been a big mess.
> 
> Nacked-by: Russ Anderson <rja@sgi.com>
> 
> 
> > Signed-off-by: Matthew Garrett <matthew.garrett@nebula.com>
> > ---
> > Actually, I guess we also want this on CONFIG_IPMI_HANDLER for least
> > surprise
> > 
> >  drivers/acpi/Kconfig      | 2 +-
> >  drivers/char/ipmi/Kconfig | 2 ++
> >  2 files changed, 3 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/acpi/Kconfig b/drivers/acpi/Kconfig
> > index 4770de5..0e6aab9 100644
> > --- a/drivers/acpi/Kconfig
> > +++ b/drivers/acpi/Kconfig
> > @@ -162,7 +162,7 @@ config ACPI_PROCESSOR
> >  config ACPI_IPMI
> >  	tristate "IPMI"
> >  	depends on IPMI_SI
> > -	default n
> > +	default y
> >  	help
> >  	  This driver enables the ACPI to access the BMC controller. And it
> >  	  uses the IPMI request/response message to communicate with BMC
> > diff --git a/drivers/char/ipmi/Kconfig b/drivers/char/ipmi/Kconfig
> > index 0baa8fa..eea8464 100644
> > --- a/drivers/char/ipmi/Kconfig
> > +++ b/drivers/char/ipmi/Kconfig
> > @@ -5,6 +5,7 @@
> >  menuconfig IPMI_HANDLER
> >         tristate 'IPMI top-level message handler'
> >         depends on HAS_IOMEM
> > +       default y if ACPI
> >         help
> >           This enables the central IPMI message handler, required for IPMI
> >  	 to work.
> > @@ -45,6 +46,7 @@ config IPMI_DEVICE_INTERFACE
> >  
> >  config IPMI_SI
> >         tristate 'IPMI System Interface handler'
> > +       default y if ACPI
> >         help
> >           Provides a driver for System Interfaces (KCS, SMIC, BT).
> >  	 Currently, only KCS and SMIC are supported.  If
> 
> 

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

  parent reply	other threads:[~2014-02-20 23:55 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 16:28 Matthew Garrett
2014-02-18 23:26 ` Rafael J. Wysocki
2014-02-18 23:15   ` Matthew Garrett
2014-02-18 23:35     ` Rafael J. Wysocki
2014-02-18 23:25       ` Matthew Garrett
2014-02-19  0:45         ` Rafael J. Wysocki
2014-02-19  0:53           ` Corey Minyard
2014-03-12 23:00     ` Pavel Machek
2014-03-12 23:22       ` Matthew Garrett
2014-03-13  7:22         ` Pavel Machek
2014-03-13  7:24           ` Matthew Garrett
2014-03-13  8:38             ` Pavel Machek
2014-03-13 13:29               ` Corey Minyard
2014-03-16  8:53                 ` Pavel Machek
2014-02-20 20:14 ` Russ Anderson
2014-02-20 20:16   ` Matthew Garrett
2014-02-20 20:40     ` Russ Anderson
2014-02-20 20:46       ` Matthew Garrett
2014-02-20 20:59         ` Russ Anderson
2014-02-20 21:00           ` Matthew Garrett
2014-02-20 21:28             ` Russ Anderson
2014-02-20 21:39               ` Matthew Garrett
2014-02-20 22:06                 ` Russ Anderson
2014-02-20 22:26                   ` Matthew Garrett
2014-02-20 22:45                     ` Russ Anderson
2014-02-20 23:09                       ` Matthew Garrett
2014-02-20 23:59                         ` Russ Anderson
2014-02-21  0:13                           ` Matthew Garrett
2014-02-21 16:53                             ` Russ Anderson
2014-02-21  2:17                           ` Zheng, Lv
2014-02-21 16:12                             ` Matthew Garrett
2014-02-24  0:48                               ` Zheng, Lv
2014-02-21 16:33                             ` Russ Anderson
2014-02-21 13:37             ` Corey Minyard
2014-02-21 15:51               ` Matthew Garrett
2014-02-21 17:12                 ` Corey Minyard
2014-02-20 21:49         ` Russ Anderson
2014-02-20 21:51           ` Matthew Garrett
2014-02-21  0:10   ` Rafael J. Wysocki [this message]
2014-02-20 23:01 ` Russ Anderson

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=1473995.mOCKVf8skD@vostro.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.garrett@nebula.com \
    --cc=minyard@acm.org \
    --cc=rja@sgi.com \
    /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

Powered by JetHome