platform-driver-x86.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: platform-driver-x86@vger.kernel.org, mjg59@redhat.com,
	infernix <infernix@infernix.net>
Subject: Re: [PATCH 1/2] IPS driver: don't toggle CPU turbo on unsupported CPUs
Date: Thu, 23 Sep 2010 15:18:31 -0700	[thread overview]
Message-ID: <20100923151831.3ca390c6@jbarnes-desktop> (raw)
In-Reply-To: <201009232358.11026.rjw@sisk.pl>

On Thu, 23 Sep 2010 23:58:10 +0200
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> On Thursday, September 23, 2010, Jesse Barnes wrote:
> > On Thu, 23 Sep 2010 23:49:28 +0200
> > Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> > 
> > > If the CPU doesn't support turbo, don't try to enable/disable it.
> > > 
> > > Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> > > ---
> > >  drivers/platform/x86/intel_ips.c |   14 +++++++++-----
> > >  1 files changed, 9 insertions(+), 5 deletions(-)
> > > 
> > > diff --git a/drivers/platform/x86/intel_ips.c b/drivers/platform/x86/intel_ips.c
> > > index bfa9c72..71d04ef 100644
> > > --- a/drivers/platform/x86/intel_ips.c
> > > +++ b/drivers/platform/x86/intel_ips.c
> > > @@ -51,7 +51,6 @@
> > >   * TODO:
> > >   *   - handle CPU hotplug
> > >   *   - provide turbo enable/disable api
> > > - *   - make sure we can write turbo enable/disable reg based on MISC_EN
> > >   *
> > >   * Related documents:
> > >   *   - CDI 403777, 403778 - Auburndale EDS vol 1 & 2
> > > @@ -325,6 +324,7 @@ struct ips_driver {
> > >  	bool gpu_preferred;
> > >  	bool poll_turbo_status;
> > >  	bool second_cpu;
> > > +	bool turbo_toggle_allowed;
> > >  	struct ips_mcp_limits *limits;
> > >  
> > >  	/* Optional MCH interfaces for if i915 is in use */
> > > @@ -461,7 +461,8 @@ static void ips_enable_cpu_turbo(struct ips_driver *ips)
> > >  	if (ips->__cpu_turbo_on)
> > >  		return;
> > >  
> > > -	on_each_cpu(do_enable_cpu_turbo, ips, 1);
> > > +	if (ips->turbo_toggle_allowed)
> > > +		on_each_cpu(do_enable_cpu_turbo, ips, 1);
> > >  
> > >  	ips->__cpu_turbo_on = true;
> > >  }
> > > @@ -498,7 +499,8 @@ static void ips_disable_cpu_turbo(struct ips_driver *ips)
> > >  	if (!ips->__cpu_turbo_on)
> > >  		return;
> > >  
> > > -	on_each_cpu(do_disable_cpu_turbo, ips, 1);
> > > +	if (ips->turbo_toggle_allowed)
> > > +		on_each_cpu(do_disable_cpu_turbo, ips, 1);
> > >  
> > >  	ips->__cpu_turbo_on = false;
> > >  }
> > > @@ -1332,8 +1334,10 @@ static struct ips_mcp_limits *ips_detect_cpu(struct ips_driver *ips)
> > >  	 * turbo manually or we'll get an illegal MSR access, even though
> > >  	 * turbo will still be available.
> > >  	 */
> > > -	if (!(misc_en & IA32_MISC_TURBO_EN))
> > > -		; /* add turbo MSR write allowed flag if necessary */
> > > +	if (misc_en & IA32_MISC_TURBO_EN)
> > > +		ips->turbo_toggle_allowed = true;
> > > +	else
> > > +		ips->turbo_toggle_allowed = false;
> > >  
> > >  	if (strstr(boot_cpu_data.x86_model_id, "CPU       M"))
> > >  		limits = &ips_sv_limits;
> > 
> > Rafael and infernix, this patch should address the GPF in the IPS
> > driver (kernel bug 18742).
> > 
> > Matthew, since I forgot to add a link to the kernel bug in the log, can
> > you add it when you commit?
> > 
> > http://bugzilla.kernel.org/show_bug.cgi?id=18742
> 
> Can you drop the patch into the Bugzilla for completeness?
> 
> Or is it in patchwork?

Dunno about patchwork, but I just added it to the bug.

-- 
Jesse Barnes, Intel Open Source Technology Center

      reply	other threads:[~2010-09-23 22:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-23 21:49 [PATCH 1/2] IPS driver: don't toggle CPU turbo on unsupported CPUs Jesse Barnes
2010-09-23 21:49 ` [PATCH 2/2] IPS driver: verify BIOS provided limits Jesse Barnes
2010-09-23 21:53   ` Jesse Barnes
2010-09-27 17:38     ` Jesse Barnes
2010-09-23 21:51 ` [PATCH 1/2] IPS driver: don't toggle CPU turbo on unsupported CPUs Jesse Barnes
2010-09-23 21:58   ` Rafael J. Wysocki
2010-09-23 22:18     ` Jesse Barnes [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=20100923151831.3ca390c6@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=infernix@infernix.net \
    --cc=mjg59@redhat.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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;
as well as URLs for NNTP newsgroup(s).