From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nishanth Aravamudan Subject: acpi_os_sleep() Date: Tue, 13 Jul 2004 16:28:13 +0000 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <40F40D9D.3000409@us.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, kernel-janitors-qjLDD68F18O7TbgM5vRIOg@public.gmane.org List-Id: linux-acpi@vger.kernel.org Hi, In continuing to replace, where appropriate, code with msleep() calls, I ran across drivers/acpi/osl.c::acpi_os_sleep(): void acpi_os_sleep(u32 sec, u32 ms) { current->state = TASK_INTERRUPTIBLE; schedule_timeout(HZ * sec + (ms * HZ) / 1000); } I was wondering if this needed to run in TASK_INTERRUPTIBLE or whether I could go ahead and replace it with msleep() (which runs in TASK_UNINTERRUPTIBLE). Thanks, Nish ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com