HP-UX wanted the new type. It can be defined as necessary for Linux; However,I can change the default to UINT32 if that's what is used on most operating systems. The information as to thread ID can be very useful when debugging multi threaded issues, and will probably become more important as we encounter more of these. I would like to keep it around for the time being. Bob > -----Original Message----- > From: Brown, Len > Sent: Saturday, April 01, 2006 12:14 AM > To: Moore, Robert > Cc: linux-acpi@xxxxxxxxxxxxxxx > Subject: acpi_thread_id = acpi_os_get_thread_id() > > Bob, > with the new type acpi_thread_id, it seems that the thread_id grows from > 32-bits > to 64-bits on a 64-bit mahcine. > > acpi_os_get_thread_id() currently returns task.pid on Linux, > a 32-bit integer on both 32 and 64-bit machines. > > So if acpi_os_get_thread_id() is called at interrupt level, > its return value is meaningless. > > Linux doesn't define ACPI_MUTEX_DEBUG, and looks like it never will. > > Is it possible to delete the concept of acpi_os_get_thread_id()? > I'm wondering at the moment if the right thing isn't to do this: > > #define acpi_os_get_thread_id() (0) > > thanks, > -Len - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
