On Fri, Dec 01, 2000 at 02:22:11PM -0700, Gordon McNutt wrote:
> Looking at some of the examples, it appears that an RT interrupt handler
> can invoke the RT scheduler (by calling pthread_wakeup_np, sem_post,
> etc). And it looks like the scheduler is going to swap in a runnable
> task when this happens.
>
> This doesn't seem safe... I'm still thinking about it...
It is.
>
> My (limited) knowledge of interrupts & schedulers indicates that the
> scheduler should just mark the task as ready to run and return. Then,
Return to what?
> after the interrupt handling code exits, the scheduler is called to pick
> the next task to run.
Called from where?
There must be some interrupt operation that can force a scheduling
or else you have only voluntary preemption.
>
> Is the RTLinux model different, or am I just misreading something?
>
> Thanks,
>
> --Gordon
>
> -- [rtl] ---
> To unsubscribe:
> echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
> echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
> ---
> For more information on Real-Time Linux see:
> http://www.rtlinux.org/rtlinux/
--
---------------------------------------------------------
Victor Yodaiken
Finite State Machine Labs: The RTLinux Company.
www.fsmlabs.com www.rtlinux.com
-- [rtl] ---
To unsubscribe:
echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR
echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED]
---
For more information on Real-Time Linux see:
http://www.rtlinux.org/rtlinux/
