Linux does not correctly implement the ACPI specification

2006-04-08 Thread Peter Wainwright
trol method. My intention is that in future this will be used to reap unused threads. Of course, the user-configurable pool size may not be necessary. We might hard-code it. Or even allow the AML to create as many threads as necessary (assuming we trust the BIOS). Peter Wainwright (P.S. not the Apa

Re: Linux does not correctly implement the ACPI specification

2006-04-27 Thread Peter Wainwright
On Wed, 2006-04-12 at 18:56 +0200, Andi Kleen wrote: > Peter Wainwright <[EMAIL PROTECTED]> writes: > > Instead of executing all the GPE and Notify handlers in the single > > kacpid thread, we create a pool of worker threads and hand over the > > work to them. >

[RFC] [PATCH 2/2] Multi-threaded execution of ACPI control methods (continued)

2006-05-03 Thread Peter Wainwright
This patch enables the maximum size of the ACPI thread pool to be configured by a /proc filesystem entry. This limit is imposed in case a rogue BIOS DSDT tries to create too many threads. Peter Signed-off-by: Peter Wainwright <[EMAIL PROTECTED]> diff -u -r linux-2.6.16.11-prw2-old/d

[RFC] [PATCH 1/2] Multi-threaded execution of ACPI control methods

2006-05-03 Thread Peter Wainwright
default behaviour for the kernel on all platforms, however, since a careful reading of the ACPI spec suggests that the behaviour of the nx6125 DSDT is in compliance with this spec and that any BIOS may potentially require this feature. Peter Signed-off-by: Peter Wainwright <[EMAIL PROTECTED]>