[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0610081539010.3952@g5.osdl.org>
Date: Sun, 8 Oct 2006 15:42:04 -0700 (PDT)
From: Linus Torvalds <torvalds@...l.org>
To: "Duran, Leo" <leo.duran@....com>
cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Arjan van de Ven <arjan@...radead.org>,
Jeff Garzik <jeff@...zik.org>, Andi Kleen <ak@...e.de>,
discuss@...-64.org, linux-kernel@...r.kernel.org
Subject: RE: [discuss] Re: Please pull x86-64 bug fixes
On Sun, 8 Oct 2006, Duran, Leo wrote:
>
> But, allow me to cite another example to reinforce my point about the
> merit of ACPI: Staying with processor power management interfaces, how
> about 'dynamic' interfaces such as _PPC? _PPC describes to the OS the
> platform's desired behavior based on some event, like unplugging the
> power-cord on a laptop - I find merit on that kind of platform-to-OS
> communication mechanism (I don't like the idea of having the platform
> making decisions & taking actions behind the OS's back... and even if it
> had to, I like the idea of at least providing some kind of notification,
> which is possible via ACPI interfaces).
The thing is, we'd just have been much better off if Intel had just
specified some perfectly regular interrupt for a "power management event",
coming out of a PCI device for that thing (say, the southbridge?), and
just tried to standardize it.
We'd have far fewer bugs that way. As it is, we need to often know about
how the hardware works _anyway_, just to fix up the problems that not
knowing about it causes.
Linus
-
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