[EMAIL PROTECTED] wrote:
>
> On Thu, Mar 23, 2000 at 06:51:42PM +0100, David Olofson wrote:
> > Thu, 23 Mar 2000 [EMAIL PROTECTED] wrote:
> > > I'm thinking of adding RT schedulable Linux processes that run solely in user
> > > space -- when they do a syscall they fall out of RT scheduling.
> >
> > Have you found a way to replace the normal syscall layer for those threads, or
> > similar solution?
>
> This is easy to do via a variety of methods: one is simply to require that the
> user links with a special library that uses a second syscall interface and
> there are x86 specific methods in which you grab the LDT -- I think this
> is what Paolo has done although he should say.
Yes, as I told in a previous answer to similar Tomek's questions, LXRT
traps
both the Linux syscall and reserved traps at their root level. It is up
to users to install code alternatives for processing them. The problem
is that going too far along that way leads to writing a whole new
operating systems.
My opinion is that the user should care of mating its hard real time
process with a soft buddy in charge of acting as a server toward Linux
services. With RTAI APIs it is easy to do, many examples in the RTAI
distribution show that.
But I'm just one of the extended LXRT developpers.
Ciao, Paolo.
-- [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/
