From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4DFCA54B.1040405@domain.hid> Date: Sat, 18 Jun 2011 15:16:59 +0200 From: Jan Kiszka 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> In-Reply-To: <4DFCA432.3070203@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigE3B4E0F3818A1831DF4E5944" Sender: jan.kiszka@domain.hid 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: Gilles Chanteperdrix Cc: Xenomai core This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigE3B4E0F3818A1831DF4E5944 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 2011-06-18 15:12, Gilles Chanteperdrix wrote: > On 06/18/2011 03:07 PM, Jan Kiszka wrote: >> On 2011-06-18 14:56, Gilles Chanteperdrix wrote: >>> >>> Maybe in the irq handlers, we should skip the XNHTICK replay, when >>> current_domain is root_domain. >>> >> >> That would be against the purpose of the XNTICK replay (it only target= s >> that particular case). And it would still leave us with broken ipipe d= ue >> to enabled IRQs on return from the Xenomai handlers. >=20 > What I mean is that xnintr_clock_handler, we should skip the XNHTICK > replay when the current domain upon return from xnpod_schedule is not > root. From what I understand, this case only happens when xnpod_schedul= e > migrated the thread, and in that case, the tick will have been forwarde= d > during xnpod_schedule anyway. In the problematic case, ie. when the XNHTICK replay uses an invalid sched, the current domain is root. It must be root because only then the context could have been migrated to a different CPU by Linux. So this does not help to avoid having to reload sched. Jan --------------enigE3B4E0F3818A1831DF4E5944 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk38pUsACgkQitSsb3rl5xRo/gCeIy+poDX/GFN6tWo/nTBjdAxC yxsAoJLiAEACo8n13gWvOpDOgIN8x0pt =XDqj -----END PGP SIGNATURE----- --------------enigE3B4E0F3818A1831DF4E5944--