Re: Question on Schedule and Preemption

> If the current task is running and thus not yet exiting (!current->exit_state)
> and is also in an atomic code section (i.e. under lock), it shouldn't call
> any reschedule function (which also happens by just calling msleep(): use
> mdelay() instead in that case!).
> 

actually don't use mdelay, but change your code so that you CAN sleep :)


-
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/

---

• Follow-Ups:
  • Re: Question on Schedule and Preemption
    • From: Andreas Mohr <[email protected]>

• References:
  • Question on Schedule and Preemption
    • From: "Liu haixiang" <[email protected]>
  • Re: Question on Schedule and Preemption
    • From: Andreas Mohr <[email protected]>

• Prev by Date: [PATCH] Documentation: no more device ids
• Next by Date: Re: PATCH [2/3]: Provide generic backlight support in IBM ACPI driver
• Previous by thread: Re: Question on Schedule and Preemption
• Next by thread: Re: Question on Schedule and Preemption
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]