From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Ingo Molnar <mingo@elte.hu>
Cc: Len Brown <lenb@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
x86@kernel.org, linux-pm@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] x86 APM: delete Linux kernel APM support
Date: Fri, 25 Mar 2011 23:33:23 +0100 [thread overview]
Message-ID: <201103252333.23880.rjw@sisk.pl> (raw)
In-Reply-To: <20110325113048.GC29521@elte.hu>
On Friday, March 25, 2011, Ingo Molnar wrote:
>
> * Len Brown <lenb@kernel.org> wrote:
>
> > > Thus from a maintenance POV APM has not been much of a drag on the x86
> > > maintainer side. Sure, we do not test it, but that's the case with most of
> > > the obsolete drivers in the kernel.
> > >
> > > The principle is that as long as there's no ongoing drag, the cost of
> > > carrying obsolete drivers is minimal - and the unknown cost of screwing
> > > someone in a big way by removing hardware support is hard to measure
> > > reliably. So we are cautious and err on the side of supporting too much
> > > hardware.
> >
> > I think this reasoning would apply in 2006, but that was 5 years ago.
>
> I cited a few real examples:
>
> > > Beyond the lack of a upstream-visible feature-removal-schedule entry, we
> > > still have an Arcnet driver which hardware was obsoleted by Ethernet in the
> > > late 80s, and we still have i486 support and those are *much* older than
> > > APM.
>
> So how does your reasoning not apply to those drivers? There's several which
> are older than APM support.
>
> We had this really big battle about x86/Voyager two years ago, which x86
> subarchitecture literally had just a single user left, and the code was more
> intrusive than APM. Even there after much flaming the eventual consensus was
> that we'd accept it back if it was done cleanly, as part of the new-style
> x86_platform code.
>
> Given that APM fits into the current PM frameworks there's no such problem here
> that i can see.
Well, it kind of does but not really. :-)
The main problem with APM is that nobody really works on it and I'm not sure
if there are any active users. At least no one reports any problems with it,
which is kind of surprising, given the number of chages we've made in the PM
core for the last couple of years. So quite likely it's just become
non-functional over time anyway, but we have no confirmation.
Thanks,
Rafael
next prev parent reply other threads:[~2011-03-25 22:33 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.02.1103232321070.3848@x980>
[not found] ` <20110324154505.934a56a0.sfr@canb.auug.org.au>
2011-03-24 7:39 ` [PATCH] APM: delete APM in Linux-2.6.40 Len Brown
2011-03-24 8:16 ` [PATCH] x86 APM: delete Linux kernel APM support Len Brown
2011-03-24 8:31 ` [PATCH] x86 APM: delete Linux kernel APM support (v2) Len Brown
2011-03-24 16:01 ` Andi Kleen
2011-03-24 8:39 ` [PATCH] x86 APM: delete Linux kernel APM support Ingo Molnar
2011-03-24 23:49 ` Len Brown
2011-03-25 11:30 ` Ingo Molnar
2011-03-25 12:38 ` Ingo Molnar
2011-03-25 12:41 ` Ingo Molnar
2011-03-25 22:33 ` Rafael J. Wysocki [this message]
2011-03-26 4:35 ` Len Brown
2011-04-08 6:25 ` Pavel Machek
2011-04-08 20:55 ` H. Peter Anvin
2011-04-11 13:05 ` Pavel Machek
2011-04-11 18:19 ` H. Peter Anvin
2011-04-13 13:30 ` Pavel Machek
2011-03-26 5:01 ` Len Brown
2011-03-26 9:31 ` Ingo Molnar
2011-03-27 21:40 ` Ondrej Zary
2011-03-28 4:51 ` Ingo Molnar
2011-03-28 5:43 ` H. Peter Anvin
2011-03-28 12:57 ` H. Peter Anvin
2011-03-28 5:18 ` Ingo Molnar
2011-03-25 15:41 ` Calvin Walton
2011-03-24 8:18 ` [PATCH] APM: delete APM in Linux-2.6.40 Stephen Rothwell
2011-03-24 8:38 ` Alexander Stein
2011-03-24 10:21 ` Henrique de Moraes Holschuh
2011-03-24 23:05 ` Len Brown
2011-03-25 1:07 ` Henrique de Moraes Holschuh
2011-03-25 1:34 ` Len Brown
2011-04-04 16:44 ` Pavel Machek
2011-04-04 20:18 ` Len Brown
2011-03-24 12:15 ` Ondrej Zary
2011-03-24 23:29 ` Len Brown
2011-03-25 8:07 ` Ondrej Zary
2011-03-26 5:09 ` Len Brown
2011-04-02 21:40 ` Yuhong Bao
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=201103252333.23880.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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
Powered by JetHome