From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Miernik <miernik@ffii.org>
Cc: linux-acpi@vger.kernel.org
Subject: Re: why no duration[00000000000000000000] for C1 state?
Date: Sat, 4 Feb 2006 22:32:58 +0100 [thread overview]
Message-ID: <20060204213258.GA21284@isilmar.linta.de> (raw)
In-Reply-To: <20060129100722.1359.0.NOFFLE@localhost.localdomain.local>
Hi,
On Sun, Jan 29, 2006 at 11:07:22AM +0100, Miernik wrote:
> On
> http://ck.kolivas.org/patches/dyn-ticks/split-out/C-States-3_accounting_of_sleep_times.patch
> it says: "Also track the actual time spent in C-States (C2 upwards, we
> can't determine this for C1), not only the number of invocations." Why
> we cannot have time spent in C1?
Once an interrupt awakes the CPU, the interrupt is handled immediately if
the CPU was in C1, while on C2 or C3, the idle handler is executed at first,
allowing to measure the "stop" time.
> Would it also be possible to have time
> spent in C0 and/or total time of the statistics? And/or % of time spent
> in each state?
That can be done in userspace.
Dominik
prev parent reply other threads:[~2006-02-04 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-29 10:07 why no duration[00000000000000000000] for C1 state? Miernik
2006-02-04 21:32 ` Dominik Brodowski [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=20060204213258.GA21284@isilmar.linta.de \
--to=linux@dominikbrodowski.net \
--cc=linux-acpi@vger.kernel.org \
--cc=miernik@ffii.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox