From: Len Brown <lenb@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Pavel Machek <pavel@ucw.cz>,
linux-pm@lists.linux-foundation.org,
Pierre Ossman <drzeus-list@drzeus.cx>,
LKML <linux-kernel@vger.kernel.org>,
Adam Belay <abelay@novell.com>, Lee Revell <rlrevell@joe-job.com>
Subject: Re: [linux-pm] [PATCH] cpuidle: avoid singing capacitors
Date: Fri, 14 Mar 2008 00:13:58 -0400 [thread overview]
Message-ID: <200803140013.59146.lenb@kernel.org> (raw)
In-Reply-To: <20080313104217.GH2522@one.firstfloor.org>
On Thursday 13 March 2008, Andi Kleen wrote:
> On Thu, Mar 13, 2008 at 09:10:48AM +0100, Pavel Machek wrote:
> > Hi!
> >
> > > > > USB keeps processor out of C3 in many cases.
> > > >
> > > > I figured that was the case. But I did not see any difference in powertop.
> > >
> > > Modern Intel mobile processors have a feature called "C2 popup"
> > > that allows the processor to retire DMA from C3 without
> > > breaking into C0. Instead the processor pops up to C2
> > > where the cache snoop can allow the DMA to retire --
> > > then it returns to C3, all transparent to software.
> >
> > Does that mean we should go to C3 on modern intels, even with
> > busmaster going on, so that cpu can keep going C2..C3..C2 as needed?
That decision has already been made for us.
BM_STS has been made a no-op on recent processors.
It reports bus activity only for a small sub-set of
south-bridge devices. Otherwise it tells us there
is none and that we should proceed into C3.
> C3 is still more expensive power wise to enter, so entering C3 just
> to let it immediately go back to C2 for bus mastering would be likely
> still a loss over staying at C2.
The newer the processor, the less exposed we area to this scenario.
cheers,
-Len
next prev parent reply other threads:[~2008-03-14 4:15 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 18:38 [RFC][PATCH] cpuidle: avoid singing capacitors Pierre Ossman
2008-02-29 21:44 ` Lennart Sorensen
2008-03-01 12:31 ` Pierre Ossman
2008-03-01 13:40 ` Pierre Ossman
2008-03-02 2:27 ` Lee Revell
2008-03-02 14:17 ` Pierre Ossman
2008-03-03 12:36 ` Andi Kleen
2008-03-03 20:18 ` [PATCH] " Pierre Ossman
2008-03-03 20:46 ` Pavel Machek
2008-03-03 21:03 ` Pierre Ossman
2008-03-03 21:08 ` Pavel Machek
2008-03-03 21:14 ` Pallipadi, Venkatesh
2008-03-03 21:17 ` Pierre Ossman
2008-03-03 22:04 ` Pallipadi, Venkatesh
2008-03-03 23:05 ` [linux-pm] " Alan Stern
2008-03-03 23:10 ` Andi Kleen
2008-03-04 4:00 ` Dave Jones
2008-03-04 6:14 ` Pierre Ossman
2008-03-04 17:19 ` Pierre Ossman
2008-03-04 17:29 ` Andi Kleen
2008-03-04 17:30 ` Pierre Ossman
2008-03-04 17:43 ` Andi Kleen
2008-03-04 18:04 ` Pierre Ossman
2008-03-04 18:34 ` Andi Kleen
2008-03-05 6:04 ` Pierre Ossman
2008-03-05 15:48 ` Andi Kleen
2008-03-05 16:53 ` Pierre Ossman
2008-03-05 17:32 ` Andi Kleen
2008-03-04 19:01 ` Pallipadi, Venkatesh
2008-03-05 6:02 ` Pierre Ossman
2008-03-05 8:40 ` Pierre Ossman
2008-03-05 9:03 ` Pavel Machek
2008-03-05 13:42 ` Pierre Ossman
2008-03-05 13:47 ` Pavel Machek
2008-03-05 13:52 ` Pierre Ossman
2008-03-06 8:27 ` Pierre Ossman
2008-03-09 14:16 ` Pierre Ossman
2008-03-09 18:19 ` Rafael J. Wysocki
2008-03-09 18:50 ` Alan Stern
2008-03-09 19:30 ` Henrique de Moraes Holschuh
2008-03-09 20:14 ` Pierre Ossman
2008-03-09 20:41 ` Henrique de Moraes Holschuh
2008-03-09 20:54 ` Henrique de Moraes Holschuh
2008-03-10 10:00 ` Pavel Machek
2008-03-10 12:49 ` Pierre Ossman
2008-03-10 13:04 ` Andi Kleen
2008-03-10 13:29 ` Pierre Ossman
2008-03-12 19:11 ` Len Brown
2008-03-13 8:10 ` Pavel Machek
2008-03-13 10:42 ` Andi Kleen
2008-03-14 4:13 ` Len Brown [this message]
2008-03-13 16:34 ` Pierre Ossman
2008-03-13 16:47 ` Pallipadi, Venkatesh
2008-03-13 17:44 ` Pierre Ossman
2008-03-13 17:49 ` Pierre Ossman
2008-03-14 19:40 ` Pierre Ossman
2008-03-14 21:15 ` Pallipadi, Venkatesh
2008-03-15 0:41 ` Pierre Ossman
2008-03-11 7:51 ` Pierre Ossman
2008-03-11 10:48 ` Andi Kleen
2008-03-11 15:20 ` Pierre Ossman
2008-03-11 17:31 ` Pierre Ossman
2008-03-12 19:17 ` Len Brown
2008-03-12 20:31 ` Len Brown
2008-03-04 9:40 ` Andi Kleen
2008-03-03 23:09 ` Andi Kleen
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=200803140013.59146.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=abelay@novell.com \
--cc=andi@firstfloor.org \
--cc=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--cc=rlrevell@joe-job.com \
/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