mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: linux-pm@lists.linux-foundation.org
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Power management minisummit at LPC
Date: Mon, 19 Jul 2010 14:55:52 +0100	[thread overview]
Message-ID: <20100719135552.GB15785@srcf.ucam.org> (raw)

I'm running a power management session at the Linux Plumbers Conference 
this year. Unlike most traditional conferences where the aim is to 
present new solutions, LPC focuses on discussing the problems that we 
haven't completely solved yet.

This has been an especially interesting year in the field. We've landed 
the infrastructure for generic runtime power management, glued that into 
PCI and started implementing that at the driver level. pm_qos is being 
reworked to improve performance and scalability as we start seeing more 
drivers that need to express their own constraints. And, of course, we 
had the wakelock/suspend blockers conversation that didn't end in a 
terribly satisfactory manner, although Rafael is now working on an 
implementation that presents equivalent functionality with a different 
userspace API. Runtime full-system suspend isn't solved yet either - the 
current cpuidle-based solution doesn't work well on multicore systems. 
And maybe we could be more aggressive still by looking at reclocking 
more system components on the fly even if the existing interfaces don't 
allow that. Do we have all the hooks we need to identify which system 
resources are being used? Are we doing the best we can in terms of 
avoiding trading off performance for power savings?

Head to 
http://www.linuxplumbersconf.org/2010/ocw/events/LPC2010MC/proposals to 
add a suggestion for a topic to be discussed at the miniconference. It's 
also possible to submit a proposal for the main presentation tyou have 
menrelated that you think would be appropriate for a wider audience, 
then please propose it there as well.

-- 
Matthew Garrett | mjg59@srcf.ucam.org

                 reply	other threads:[~2010-07-19 13:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20100719135552.GB15785@srcf.ucam.org \
    --to=mjg59@srcf.ucam.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.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

all inboxes | Powered by JetHome®