On Thu, May 04, 2000 at 12:59:33PM +0530, santhosh m kumar wrote:
> Hi,
>
> In pthread_make_periodic_np and few other function in rtl_sched.c,
> rtl_no_interrupts is called and then rtl_schedule is called. After which
> rtl_restore_interrupts is done.
> Will this not cause some problems, that is the interrupts will be disable
> when the new task is running. If i am wrong, can any one tell me where
> exactly is the rtl_restore_interrupts done.
The scheduler does
save the interrupt status
disable interrupts
switch to new thread
restore interrupt status saves for this thread.
So the new thread will run with the correct interrupt status.
>
> One more question, is priority inversion supported in RTL.
Priority inversion is a design issue. RTLinux is designed so that the
RT threads never wait for Linux unless they request to do so. You should
design your RT application so that lower priority threads do not
hold resources needed by higher priority threads, except when they have
disabled scheduling. It's not very hard unless the application is too
complex -- and then nothing will help anyways except for a redesign.
>
> Thanks and Regards
> Santhosh
> -- [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
FSMLabs: www.fsmlabs.com www.rtlinux.com
FSMLabs is a servicemark and a service of
VJY Associates L.L.C, New Mexico.
-- [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/
