public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Larry Baker <baker@usgs.gov>
Cc: linux-acpi@vger.kernel.org, Rob E Russell <robr@us.ibm.com>
Subject: Re: Wishlist: Disable C6 in intel_idle for Model 44 processors
Date: Wed, 12 Jun 2013 19:32:49 +0100	[thread overview]
Message-ID: <20130612183249.GA20957@srcf.ucam.org> (raw)
In-Reply-To: <1BD2BF18-8FAA-4633-8B6D-7CA2D6AE67AC@usgs.gov>

On Wed, Jun 12, 2013 at 11:11:21AM -0700, Larry Baker wrote:

> The processor errata is operating system agnostic.  I suspect the BIOS 
> workaround they envision would be a feature in the BIOS to limit the 
> choice of C states to be used.  The IBM BIOS has such a setting, and 
> the default value is to completely disable C states.  However, 
> intel_idle ignores the BIOS setting.

No, the BIOS workaround will typically be to program the memory 
controller such that the problem isn't triggered. If you're having 
latency-related issues then the appropriate fix is to use the pm_qos 
interface that's present in RHEL 6 and the upstream kernel, and you can 
do so in RHEL using the ktune command. 

-- 
Matthew Garrett | mjg59@srcf.ucam.org

  reply	other threads:[~2013-06-12 18:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-11 21:30 Wishlist: Disable C6 in intel_idle for Model 44 processors Larry Baker
2013-06-11 21:34 ` Larry Baker
2013-06-12 13:40 ` Matthew Garrett
2013-06-12 18:11   ` Larry Baker
2013-06-12 18:32     ` Matthew Garrett [this message]
2013-06-14 19:32       ` Len Brown
2013-06-14 20:23         ` Larry Baker
     [not found]           ` <OF3D706B0A.D5540D6C-ON85257B8A.0076278F-85257B8A.0076E4B1@us.ibm.com>
2013-06-14 22:40             ` Larry Baker
2013-06-20 19:22         ` Larry Baker
2013-06-16  3:29   ` Henrique de Moraes Holschuh

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=20130612183249.GA20957@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=baker@usgs.gov \
    --cc=linux-acpi@vger.kernel.org \
    --cc=robr@us.ibm.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