linux-kernel - Re: [linux-pm] Power management minisummit at Linux Plumbers Conference (November 3-5)

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]

Date:	Tue, 03 Aug 2010 15:30:56 -0500
From:	Mike Turquette <mturquette@...com>
To:	Matthew Garrett <mjg59@...f.ucam.org>
CC:	"linux-pm@...ts.osdl.org" <linux-pm@...ts.osdl.org>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [linux-pm] Power management minisummit at Linux Plumbers Conference
 (November	3-5)

Matthew Garrett wrote:
> I'm planning on finalising the schedule for the power management 
> minisummit at the Linux Plumbers Conference by the end of this week. If 
> anyone has topics that they'd like to discuss (or be discussed, if you 
> can't make it) then please let me know or register at 
> http://www.linuxplumbersconf.org/2010/ocw/events/proposals/ and file a 

That link did not really work for me, but I think I found the right 
place after a few clicks.

> proposal there. We're likely to be concentrating on userspace/kernel 
> interaction rather than pure kernel topics, so if you've got anything to 
> say about how we can handle application requirements without 
> compromising on our power savings then we'd love to hear from you.

Just FYI, I proposed a discussion on the issues that create such a large 
power gap between a CPUIdle-only system and a system with suspend (with 
the assumption that the lowest C-state can be hit by both).

I don't really want to present a formal lecture on it, but it would be 
nice to discuss with the group what can be done to shrink that gap a 
little in kernel space (badly behaving timers in platform-independent 
code) and in userspace (power-aware timers, coalescing timers, etc).

This is not intended to be another suspend-blocker discussion, but more 
of a discussion on what it takes to get CPUIdle to be more effective.

Regards,
Mike
--
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/