BOUNCE rtl@rtlinux.org: Approval required: (fwd)

[Der Herr Hofrat <der.herr@hofr.at>]

>From owner-rtl Sat Jul  7 02:07:31 2001
Received: from hq.fsmlabs.com (localhost [[UNIX: localhost]])
	by hq.fsmlabs.com (8.11.2/8.11.2) with ESMTP id f6787TZ22823
	for <rtl@fsmlabs.com>; Sat, 7 Jul 2001 02:07:30 -0600
Received: (qmail 7093 invoked by uid 1000); 7 Jul 2001 08:00:12 -0000
Date: Sat, 7 Jul 2001 12:00:12 +0400
From: Michael Barabanov <baraban@fsmlabs.com>
To: Shlomi Rechtman <srechtma@allot.com>
Cc: "'rtl@fsmlabs.com'" <rtl@fsmlabs.com>
Subject: Re: [rtl] rt_inux interrupt
Message-ID: <20010707120012.A6961@fsmlabs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E8EEE94DC55DD2418140866BC34AFD6838E515@exg.allot.com>
User-Agent: Mutt/1.3.18i
Organization: FSMLabs

Shlomi Rechtman (srechtma@allot.com) wrote:
> Hi,
> At  Man page Index it was written that 
> "The following functions should not be used 
> in interrupt handler: pthread_delete_np ,pthread_wait_np ..."
> 
> does  "interrupt handler" relate to regular linux interrupt handler or also
> to rt_linux interrupt handler ?

Well, you could run use those functions
in a Linux interrupt handler, although I don't see any reason to do it.

> that is to say: can I do used them insdie a function
>  which if I register to rt_linux hanler ?

Absolutely not. The reason is that blocking functions like
pthread_wait_np block the current thread.
When an RTLinux interrupt handler executes, the current thread may
be any thread.

Michael.

----- End of forwarded message from owner-rtl@fsmlabs.com -----