linux-kernel - RE: [discuss] Re: Please pull x86-64 bug fixes

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:	Sun, 8 Oct 2006 15:59:56 -0500
From:	"Duran, Leo" <leo.duran@....com>
To:	"Linus Torvalds" <torvalds@...l.org>
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 Fri, 6 Oct 2006, Linus Torvalds wrote:

>On Fri, 6 Oct 2006, Duran, Leo wrote:
>> So, one can argue that there's merit on having ACPI
>
>Not really.
>
>The thing is, you have two choices:
> - define interfaces in hardware
> - not doing so, and then trying to paper it over with idiotic tables.

I would have to agree that having HW describe itself makes sense, and
would certainly negate the need for 'static' ACPI tables that attempt
doing that.

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).

Leo Duran.

-
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/