On Mon, Nov 20, 2000 at 06:54:23PM +0200, Koxaras Aris wrote:
> Hello,
> 
>         I'm trying to develop a small application on RTlinux and i have
> four questions.
> 
> a) Is there a way for my periodic RT task to figure out what was the state
> of the processor before the interruption? kernel or user mode?

Not any machine independent way, but it's not hard to find the data in the
linux thread structure.
> 
> b) What is the difference between local/global and soft/hard irq in the
> source of RTlinux.

Mostly important on SMP processors where there is a global interrupt controller
for I/O devices that are shared by the processors and local interrupts such as the
on chip timer.

> c) I want my RT task to do the following thing.
>   i) disable the delivery of interrupts to linux, by marking them pending
>  ii) enable the interrupts to linux, and deliver the pending signals to
> linux
Linux interrupts are never delivered to Linux while the RT thread is running
but are delivered automatically when the RT threads are idle.

>  [ BUT hardware interrupts should be caught by RT linux. ]
> 
> d) Is it possible for my RT task to call some kernel functions, and if so
> what are they? For instance under what circumstances can I call
> schedule() from my RT task.


You may _never_ call schedule from an RT thread. You can call rtl_schedule, but 
calling Linux schedule makes no sense.


> 
> TIA
> Koxaras Aris
> 
> 
> -- [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/

Reply via email to