All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Xiaoning Ding <dingxn@ymail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: a question about p4_clockmod module on Xeon quad core processors
Date: Wed, 28 Jan 2009 21:45:39 -0500	[thread overview]
Message-ID: <20090129024539.GA17541@redhat.com> (raw)
In-Reply-To: <630240.73962.qm@web59913.mail.ac4.yahoo.com>

[please don't top-post]

On Wed, Jan 28, 2009 at 06:06:37PM -0800, Xiaoning Ding wrote:
 
 > >  > I have tried the p4-clockmod module in Linux kernel
 > > 2.6.29 on Xeon 5355 quad-core CPUs with no luck. It seems
 > > current p4-clockmod driver still cannot support Intel Quad
 > > core processors, right? 
 > >  > 
 > >  > I know I can also use acpi-cpufreq. It can only scale
 > > down the frequence from 2.67GHz to 2GHz. But I need some
 > > lower frequencies for some experiments.
 > > 
 > > p4-clockmod doesn't change the processor frequency.
 > > Because of common misconceptions like this, the user
 > > interface has been removed.
 > > 
 > > In 2.6.29, the clock modulation code is called directly
 > > from ACPI
 > > whenever thermal events indicate that throttling is
 > > necessary.
 > > 
 > Thanks for the correction. 
 > My experiments need to reduce CPU speed. However, I can only reduce the speed by about 30% (from 2.67GHz to 2GHz) with ACPI. That is not enough for the experiments. 

The ACPI P-states are nearly always correct, so you won't be
able to go below 2GHz on this system.

 > p4-clockmod has not been removed from 2.6.29. It is under the same directory as acpi-cpufreq (arch/x86/kernel/cpu/cpufreq). So I thought it was an alternative approach. But I could not get it loaded.

The driver is present, the _user interface_ has been removed.

	Dave

-- 
http://www.codemonkey.org.uk

  reply	other threads:[~2009-01-29  2:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 20:17 a question about p4_clockmod module on Xeon quad core processors Xiaoning Ding
2009-01-27 21:23 ` Arjan van de Ven
2009-01-29 16:12   ` Xiaoning Ding
2009-01-28 21:02 ` Dave Jones
2009-01-29  2:06   ` Xiaoning Ding
2009-01-29  2:45     ` Dave Jones [this message]
2009-01-29 16:32       ` Xiaoning Ding
2009-01-29 17:08         ` Dave Jones
2009-01-29 12:27   ` Michael Tokarev
2009-01-29 17:24     ` Dave Jones
2009-01-29 19:40       ` Xiaoning Ding
2009-01-29 19:54         ` Dave Jones
2009-01-28 21:05 ` Wes Felter
2009-01-29  2:11   ` Xiaoning Ding
2009-01-29 20:47     ` Wes Felter
2009-01-30  1:12       ` Xiaoning Ding

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=20090129024539.GA17541@redhat.com \
    --to=davej@redhat.com \
    --cc=dingxn@ymail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.