From: Dominik Brodowski <linux-X3ehHDuj6sIIGcDfoQAp7OTW4wlIGRCZ@public.gmane.org>
To: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
Cc: Shaohua Li <shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
ACPI-ML <linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Pallipadi Venkatesh
<venkatesh.pallipadi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [RFC 2/2] new C-state policy
Date: Wed, 11 Jan 2006 14:51:13 +0100 [thread overview]
Message-ID: <20060111135113.GA11960@isilmar.linta.de> (raw)
In-Reply-To: <43C4EA5D.9040907-l3A5Bk7waGM@public.gmane.org>
Hi,
On Wed, Jan 11, 2006 at 12:22:05PM +0100, Thomas Renninger wrote:
> >What to do once bm_activity is or was detected, yes. How to determine
> >whether there is current bus mastering activity, no -- that's core stuff,
> >not policy stuff.
> >
> I had the experience that tweaking how bm_activity is detected could help a
> lot.
I think we still don't speak about the same topic:
a) how to detect bus mastering activity?
acpi_get_register(ACPI_BITREG_BUS_MASTER_STATUS, &bm_status, ACPI_MTX_DO_NOT_LOCK);
if (errata.piix4.bmisx) {
if ((inb_p(errata.piix4.bmisx + 0x02) & 0x01)
|| (inb_p(errata.piix4.bmisx + 0x0A) & 0x01))
pr->power.bm_activity++;
}
=> generic
b) what to do?
demote/allow faulty transition/...
=> driver-specific
So all I want is the following:
static int acpi_processor_bm_status(void) {
u32 bm_status;
acpi_get_register(ACPI_BITREG_BUS_MASTER_STATUS, &bm_status, ACPI_MTX_DO_NOT_LOCK);
if (bm_status)
return 1;
else if (errata.piix4.bmisx) {
if ((inb_p(errata.piix4.bmisx + 0x02) & 0x01)
|| (inb_p(errata.piix4.bmisx + 0x0A) & 0x01))
return 1;
}
return 0;
}
in order to not having to copy this code into each policy. What to do with
the return value of acpi_processor_bm_status() is then up to the policy.
Dominik
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-01-11 13:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 4:12 [RFC 2/2] new C-state policy Shaohua Li
[not found] ` <1136866376.5750.29.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2006-01-10 23:17 ` Dominik Brodowski
[not found] ` <20060110231711.GB30356-JwFqNg2GrOVrgjWwlLH9qw@public.gmane.org>
2006-01-11 2:00 ` Shaohua Li
[not found] ` <1136944855.5750.61.camel-U5EdaLXB8smDugQYiPIPGdh3ngVCH38I@public.gmane.org>
2006-01-11 8:04 ` Dominik Brodowski
[not found] ` <20060111080402.GB599-JwFqNg2GrOVrgjWwlLH9qw@public.gmane.org>
2006-01-11 11:22 ` Thomas Renninger
[not found] ` <43C4EA5D.9040907-l3A5Bk7waGM@public.gmane.org>
2006-01-11 13:51 ` Dominik Brodowski [this message]
[not found] ` <20060111135113.GA11960-JwFqNg2GrOVrgjWwlLH9qw@public.gmane.org>
2006-01-11 14:19 ` Thomas Renninger
2006-01-12 2:54 ` Shaohua Li
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=20060111135113.GA11960@isilmar.linta.de \
--to=linux-x3ehhduj6siigcdfoqap7otw4wligrcz@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shaohua.li-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=trenn-l3A5Bk7waGM@public.gmane.org \
--cc=venkatesh.pallipadi-ral2JQCrhuEAvxtiuMwx3w@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