Posted Oct 8, 2009 14:16 UTC (Thu) by nix
Parent article: Concurrency-managed workqueues
The ACPI code had bound a workqueue thread to CPU 0 because some operations corrupt the system if run anywhere else
Is this just BIOSes being their usual malevolently incompetent selves, or is there a rational reason for this requirement? Because my first impression when reading this was 'WTF WTF WTF'...
to post comments)