From: Pavel Machek <pavel@ucw.cz>
To: "Tippett, Matthew" <matthew.tippett@amd.com>
Cc: Willy Tarreau <w@1wt.eu>, Matthew Garrett <mjg59@srcf.ucam.org>,
"Langsdorf, Mark" <mark.langsdorf@amd.com>,
lenb@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, "Li, Samuel" <Samuel.Li@amd.com>
Subject: Re: [PATCH][ACPI] AC/DC notifier
Date: Wed, 7 Oct 2009 09:31:21 +0200 [thread overview]
Message-ID: <20091007073121.GA31245@elf.ucw.cz> (raw)
In-Reply-To: <4ACB59E2.3000600@amd.com>
On Tue 2009-10-06 10:53:22, Tippett, Matthew wrote:
> (Resending as text-only - sorry)
>
> Bringing this item back up again.
>
> I am not suggesting that the application of any particular policy
> appears within the kernel or userspace or a secondary policy engine.
> In general I am also against codifying policy within drivers.
>
> I am interested seeing the ACPI notifier mechanism expanded to allow
> AC/DC state changes propagate to other kernel drivers without requiring
> a userspace in between.
>
> I can continue to come up with real scenarios that would possibly
> require kernel-to-kernel notification, but would rather focus this
> discussion of the pure technical issues associated with adding the
> notifier to the AC/DC ACPI subsystem.
Please do. So far you did not show valid use for such notifier.
(Ok, I know of one. Old amd64 notebooks had cpufreq scaling enabled,
with battery unable to supply enough current to feed the CPU at
highest cpufreq setting. At that point, scaling cpufreq down at unplug
is correctness issue, and AC/DC notifier in kernel makes
sense.)
So... what do you want to use it for?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-10-07 7:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <FFAE0590FF35E441901B67BD8BA62E950245ABD9@storexmb3.amd.com>
2009-08-12 0:55 ` [PATCH]AC/DC notifier Matthew Garrett
2009-08-14 16:32 ` [PATCH][ACPI] AC/DC notifier Pavel Machek
2009-08-16 7:40 ` [PATCH]AC/DC notifier Willy Tarreau
2009-10-06 14:53 ` Tippett, Matthew
2009-10-07 7:31 ` Pavel Machek [this message]
2009-10-07 8:16 ` [PATCH][ACPI] AC/DC notifier Dave Airlie
2009-10-07 14:05 ` [PATCH]AC/DC notifier Matthew Garrett
2009-10-07 17:00 ` [PATCH][ACPI] AC/DC notifier Tippett, Matthew
2009-08-11 20:15 Mark Langsdorf
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=20091007073121.GA31245@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=Samuel.Li@amd.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.com \
--cc=matthew.tippett@amd.com \
--cc=mjg59@srcf.ucam.org \
--cc=w@1wt.eu \
/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;
as well as URLs for NNTP newsgroup(s).