All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mattia Dongili <malattia@linux.it>
To: CPUFreq Mailing List <cpufreq@lists.linux.org.uk>
Subject: [RFC][PATCH 0/0] measure speedstep-ich transition latency at CPU initialization
Date: Wed, 30 Nov 2005 00:58:31 +0100	[thread overview]
Message-ID: <11333087113994-git-send-email-malattia@linux.it> (raw)
In-Reply-To: 

Hello,                                      
a foreword: this is my first patch here, it surely needs more work but I'd
appreciate some comments before going too far on the wrong lane.  Oh, I'm also
trying to use some git automation to send the patch, hopefully you won't
receive too many dups :)

The 2 patches are trying to implement the suggested runtime measurement
of transition latency on speedstep ich chipsets to offer the
allow the usage of the dynamic governors to ICH[234]-M owners (like me).

The first patch moves away PMBASE reading and only performs it at
cpufreq_register_driver time by exiting with -ENODEV if unable to read
the value. (git seems a little confused, I hope it's readable)

The second patch (could be split in 2 if necessary) introduces
__speedstep_set_state that performs the frequency transition without
disabling interrupts to be used in speedstep_measure_latency and
speedstep_get_freqs (IRQs are already disabled here).
It also implements the transition measurement if the parameter
'measure_latency' is set to a value other than 0.

The measurement is performed by means of do_gettimeofday as suggested by
Mr. Pallipadi.

Known problems:
- the patch is still missing a sanity check on the measured value
- it also introduces 2 more transitions at init time (2 in
  speedstep_get_freqs + 2 in speedstep_measure_latency) because I don't
  know if makes sense to rely (and hack) on speedstep_get_freqs to perform
  measurements.

thanks
--
mattia
:wq!

             reply	other threads:[~2005-11-29 23:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-29 23:58 Mattia Dongili [this message]
2005-11-29 23:58 ` [PATCH 1/2] Move PMBASE reading away and do it only once at initialization time Mattia Dongili
2005-11-29 23:58   ` [PATCH 2/2] Measure transition latency at driver initialization Mattia Dongili
2005-11-30 11:46     ` Eric Piel
2005-11-30 22:30       ` Mattia Dongili
2005-11-30 23:41         ` Eric Piel
2005-12-01 19:31           ` [PATCH 2/2 updated] " Mattia Dongili
2005-12-01 21:05             ` Eric Piel
2005-12-01 23:34               ` Mattia Dongili
2005-12-02 11:37                 ` Eric Piel
2005-12-02 13:34                   ` Mattia Dongili
2005-12-02 20:59                     ` Mattia Dongili
2005-12-02 23:43                       ` Eric Piel
2005-12-04 17:00                       ` Dominik Brodowski
2005-12-02  4:38               ` Ville Syrjälä
2005-11-30 11:02   ` [PATCH 1/2] Move PMBASE reading away and do it only once at initialization time Eric Piel
2005-11-30 21:00     ` Mattia Dongili
2005-12-04 16:58       ` Dominik Brodowski

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=11333087113994-git-send-email-malattia@linux.it \
    --to=malattia@linux.it \
    --cc=cpufreq@lists.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 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.