BOUNCE rtl@rtlinux.org: Approval required: Non-member submissionfrom [Tony Macabuhay <Tony@Macabuhay.org>] (fwd)

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

>From owner-rtl Wed May 23 15:38:17 2001
Received: from femail2.sdc1.sfba.home.com (femail2.sdc1.sfba.home.com [24.0.95.82])
	by hq.fsmlabs.com (8.11.2/8.11.2) with ESMTP id f4NLcHP11207
	for <rtl@fsmlabs.com>; Wed, 23 May 2001 15:38:17 -0600
Received: from Macabuhay.org ([65.0.245.66]) by femail2.sdc1.sfba.home.com
          (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP
          id <20010523213310.KRUV20675.femail2.sdc1.sfba.home.com@Macabuhay.org>
          for <rtl@fsmlabs.com>; Wed, 23 May 2001 14:33:10 -0700
Message-ID: <3B0C28C3.D51AF0F0@Macabuhay.org>
Date: Wed, 23 May 2001 14:16:51 -0700
From: Tony Macabuhay <Tony@Macabuhay.org>
Organization: Macabuhay
X-Mailer: Mozilla 4.77 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: rtl@fsmlabs.com
Subject: Re: [rtl] thread scheduling and interrupts
References: <00ff01c0e382$d392a2b0$0b00005a@hprini>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit



Rini van Zetten wrote:

> ...

> When the interrupt occurs, the high priority task is fired. runs until it
> goes asleep again. after this the low priority task get running again (it
> was stopped by the interrupt) BUT the interrupt routine is not finished yet.
> After the low priority task falls asleep, and eventualy the interrupt
> routine ends.
>

Before I answer the question, I need more information.

Why are you sleeping in an IRQH?  Or is this whay you don't want it to do?
Did you design your system such that the high-priority task only ends after
certain actions are taken within the low-priority task?

-Tony