From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4DFFA24F.4050601@domain.hid> Date: Mon, 20 Jun 2011 21:41:03 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <4DFB869F.9080006@domain.hid> <4DFB88EC.9090100@domain.hid> <4DFBA305.9000303@domain.hid> <4DFC7C0E.1090700@domain.hid> <4DFC9575.1030904@domain.hid> <4DFC95B7.8070703@domain.hid> <4DFCA09B.20609@domain.hid> <4DFCA323.6030704@domain.hid> <4DFCA432.3070203@domain.hid> <4DFCAF07.8020607@domain.hid> <4DFE189D.5030908@domain.hid> <4DFF78AA.9050904@domain.hid> <4DFF8476.2000306@domain.hid> <4DFFA19C.30000@domain.hid> In-Reply-To: <4DFFA19C.30000@domain.hid> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] [Xenomai-git] Jan Kiszka : nucleus: Fix interrupt handler tails List-Id: Xenomai life and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Xenomai core On 06/20/2011 09:38 PM, Jan Kiszka wrote: > On 2011-06-20 19:33, Gilles Chanteperdrix wrote: >> On 06/20/2011 06:43 PM, Jan Kiszka wrote: >>> On 2011-06-19 17:41, Gilles Chanteperdrix wrote: >>>> Merged your whole branch, but took the liberty to change it a bit >>>> (replacing the commit concerning unlocked context switches with comments >>>> changes only, and changing the commit about xntbase_tick). >>> >>> What makes splmax() redundant for the unlocked context switch case? IMO >>> that bug is still present. >> >> No, the bug is between my keyboard and chair. On architectures with >> unlocked context switches, the Linux task switch still happens with irqs >> off, only the mm switch happens with irqs on. > > Then why do we call xnlock_get_irqsave in > xnsched_finish_unlocked_switch? Why not simply xnlock_get if irqs are > off anyway? Because of the Xenomai task switch, not the Linux task switch. -- Gilles.