cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: cpufreq@www.linux.org.uk
Subject: Re: two test/debug/dump cpufreq modules
Date: Wed, 14 Apr 2004 12:18:06 +0100	[thread overview]
Message-ID: <20040414111806.GF24970@redhat.com> (raw)
In-Reply-To: <20040406213436.GA11147@dominikbrodowski.de>

On Tue, Apr 06, 2004 at 11:34:36PM +0200, Dominik Brodowski wrote:
 > I've just uploaded cleaned-up versions of two test modules for cpufreq which
 > might be of interest for at least some of you. They're under the GPL, of
 > course, as the MODULE_LICENSE states...
 > 
 > cpufreq-acpi_pdump
 > 
 > Dump the ACPI P-States to be found in the _PSS section of the ACPI table, as
 > well as the contents of the _PCT registers. _PDC capability bits can be
 > passed as module parameter "pdc="
 > 
 > location: http://www.brodo.de/patches/2004-04-06/cpufreq-acpi_pdump.c
 > 
 > 
 > cpufreq-tsc_test
 > 
 > Verify that the TSC-based timing code continues to function as expected
 > after cpufreq transitions by dumping the difference between TSC reads and
 > PMTMR reads [ACPI Powermanagement-Aware Timer]. Needs ACPI to work properly.
 > 
 > location: http://www.brodo.de/patches/2004-04-06/cpufreq-tsc_test.c

Very nice. The first one looks especially useful.
I'm tempted to actually merge these to keep all the modules in one place.

Opinions ?

		Dave

      reply	other threads:[~2004-04-14 11:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06 21:34 two test/debug/dump cpufreq modules Dominik Brodowski
2004-04-14 11:18 ` Dave Jones [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=20040414111806.GF24970@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@www.linux.org.uk \
    /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