From: Dominik Brodowski <linux-X3ehHDuj6sIIGcDfoQAp7OTW4wlIGRCZ@public.gmane.org>
To: Thomas Renninger <mail-smMupaH/RwJM7kwft8N7nw@public.gmane.org>
Cc: ML ACPI-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
Bruno Ducrot <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: bus master activity must be polled?
Date: Wed, 4 May 2005 23:51:28 +0200 [thread overview]
Message-ID: <20050504215128.GA7874@isilmar.linta.de> (raw)
In-Reply-To: <426CB990.9030306-smMupaH/RwJM7kwft8N7nw@public.gmane.org> <427769CB.4050802-smMupaH/RwJM7kwft8N7nw@public.gmane.org>
Hi,
Reading the ICH4-M spec from intel (doc 252337 rev. 01), p. 371 actually
increases the confusion, so I tested it:
a) is the bit _only_ set if the CPU was in C3 and got awakened from there?
ANSWER: No. Even if only C2 is used, this bit is updated.
b) will the bit stay at "1" even if there is no bus master activity going
on any longer?
ANSWER: Yes. It needs to be re-set by echo'ing "1".
c) if the bus master activity is only continuing (i.e. the transaction just
hasn't finished yet), is the bus master status set to zero?
ANSWER: No.
if (bm_status) {
pr->power.bm_activity++;
acpi_set_register(ACPI_BITREG_BUS_MASTER_STATUS,
1, ACPI_MTX_DO_NOT_LOCK);
/* instant re-check */
acpi_get_register(ACPI_BITREG_BUS_MASTER_STATUS,
&bm_status, ACPI_MTX_DO_NOT_LOCK);
if (bm_status)
bm_activity2++;
}
showed that bm_activity2 was always (almost) equal to bm_activity, at least
when I looked ;)
What does this mean?
On Tue, May 03, 2005 at 02:08:43PM +0200, Thomas Renninger wrote:
> - this is because bm_sts bit will be set when a bus master transaction
> started.
No, also when it hasn't finished yet.
I think bm_status should influence how long we disable the idle tick, not
the other way round:
check bm_status
-> if it is not set, and the other requirements are fulfilled,
go to C3 or higher
-> if it is set => only C2, don't sleep for longer than, lets say,
10 ms.
alternatively:
-> if it is set => only C2, don't sleep for longer than 1 ms, then
re-check; if bus mastering is gone and CPU load and bus master
load is low (some mask-based "weight", possibly?)
for (i=0; i<32; i++) {
weight += (bm_status & (0x1 << i)) * (33 - i);
}
then enter C3 or higher for possibly longer time.
I think we can be more aggressive in entering higher idle states if
bm_status _was_ present but is no more.
Opinions? Ideas? Test results on non-Intel CPUs/chipsets?
Dominik
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
prev parent reply other threads:[~2005-05-04 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <426CB990.9030306@renninger.de>
2005-05-03 12:08 ` bus master activity must be polled? Thomas Renninger
[not found] ` <426CB990.9030306-smMupaH/RwJM7kwft8N7nw@public.gmane.org>
[not found] ` <427769CB.4050802-smMupaH/RwJM7kwft8N7nw@public.gmane.org>
2005-05-04 21:51 ` 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=20050504215128.GA7874@isilmar.linta.de \
--to=linux-x3ehhduj6siigcdfoqap7otw4wligrcz@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mail-smMupaH/RwJM7kwft8N7nw@public.gmane.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