Hi Bodo, On Mon, 05 Mar 2007 14:56:44 +0100, Bodo Eggert wrote: > 1) Make a general resource allocation lock, if there is none.
Such a lock certainly exists, but I doubt it is public at the moment. > 2) make ACPI take this lock whenever it touches ports not allocated by itself > and release it on function return. This is costly. > 3) Make ACPI callback the allocating device if it touches allocated ranges, > and on function return. By callback, do you mean port forwarding as Rudolf Marek did, or more simple "stop touching the device" and "you can touch the device again" sort of signals? If the latter, this is no different from a mutex. > 1 + 2 will replace allocating single ports and freeing them again (so ACPI > won't > prevent e.g. the display driver from loading just because it turned on the > backlight) while preventing races with newly allocated ranges, and 3 allows > coexistence with other drivers. What benefit do you see compared to a lock taken by both AML and the hardware monitoring drivers? Care to submit a sample implementation? Thanks, -- Jean Delvare - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
