From: "Mattia Dongili" <malattia@linux.it>
To: Eric Piel <Eric.Piel@lifl.fr>
Cc: Eric Piel <eric.piel@tremplin-utc.net>,
CPUFreq Mailing List <cpufreq@lists.linux.org.uk>,
Dominik Brodowski <linux@dominikbrodowski.net>,
davej@redhat.com
Subject: Re: [PATCH 2/2 updated] Measure transition latency at driver initialization
Date: Fri, 2 Dec 2005 14:34:35 +0100 (CET) [thread overview]
Message-ID: <4792.83.103.117.254.1133530475.squirrel@picard.linux.it> (raw)
In-Reply-To: <439031F0.2090607@lifl.fr>
On Fri, December 2, 2005 12:37 pm, Eric Piel said:
> 12/02/2005 12:34 AM, Mattia Dongili wrote/a écrit:
[...]
>> problematics chipsets (current testing report values ~200uSec).
> Again, I though it was done... and then Ville showed that's it's plainly
> wrong to assume anything with speedstep-smi: it could take up to 1
> second to change of frequency or few uSec. So we should probably back
> out the smi part.
>
> What I propose: modify slightly the interface of speedstep_get_freqs():
> * if transition_latency is NULL, we don't try to update the transition
> latency,
> * otherwise we so as usual.
> Then, in speedstep-smi we can call speedstep_get_freqs() with NULL,
> voila :-)
Ok, I had something similar in mind when thinking about creating a more
general function/interface for latency measurement. We will surely need
some way to disable it.
Updated patch will follow soon.
--
mattia
:wq!
next prev parent reply other threads:[~2005-12-02 13:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 23:58 [RFC][PATCH 0/0] measure speedstep-ich transition latency at CPU initialization Mattia Dongili
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2005-12-03 0:50 [PATCH 2/2 updated] Measure transition latency at driver initialization Pallipadi, Venkatesh
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=4792.83.103.117.254.1133530475.squirrel@picard.linux.it \
--to=malattia@linux.it \
--cc=Eric.Piel@lifl.fr \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=eric.piel@tremplin-utc.net \
--cc=linux@dominikbrodowski.net \
/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