lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080313104217.GH2522@one.firstfloor.org>
Date:	Thu, 13 Mar 2008 11:42:17 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Pavel Machek <pavel@....cz>
Cc:	Len Brown <lenb@...nel.org>, linux-pm@...ts.linux-foundation.org,
	Pierre Ossman <drzeus-list@...eus.cx>,
	LKML <linux-kernel@...r.kernel.org>,
	Adam Belay <abelay@...ell.com>,
	Andi Kleen <andi@...stfloor.org>,
	Lee Revell <rlrevell@...-job.com>
Subject: Re: [linux-pm] [PATCH] cpuidle: avoid singing capacitors

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?

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.

-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ