All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	kernel-janitors-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: [Kernel-janitors] acpi_os_sleep()
Date: Tue, 13 Jul 2004 16:28:13 +0000	[thread overview]
Message-ID: <40F40D9D.3000409@us.ibm.com> (raw)

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
_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

WARNING: multiple messages have this Message-ID (diff)
From: Nishanth Aravamudan <nacc-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	kernel-janitors-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: acpi_os_sleep()
Date: Tue, 13 Jul 2004 16:28:13 +0000	[thread overview]
Message-ID: <40F40D9D.3000409@us.ibm.com> (raw)

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

             reply	other threads:[~2004-07-13 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 16:28 Nishanth Aravamudan [this message]
2004-07-13 16:28 ` acpi_os_sleep() Nishanth Aravamudan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40F40D9D.3000409@us.ibm.com \
    --to=nacc@us.ibm.com \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=kernel-janitors-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.