From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 5 Apr 2022 17:53:20 +0200 (CEST) From: Richard Weinberger Message-ID: <1433861802.219536.1649174000463.JavaMail.zimbra@nod.at> In-Reply-To: <54aa3260-9a9b-dbdb-90a8-6395fd86fc28@siemens.com> References: <20220405114052.7385-1-richard@nod.at> <94940f791d07b0f2e4f8594b26aa47680a024d0b.camel@siemens.com> <54aa3260-9a9b-dbdb-90a8-6395fd86fc28@siemens.com> Subject: Re: [PATCH] xnthread_relax: Make sure wakework irq work has a stack MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Florian Bezdeka , xenomai ----- Urspr=C3=BCngliche Mail ----- > Von: "Jan Kiszka" > I would like to have an explanation or prove points (traces, assertions) > that we actually see xnthread_relax overtaking the delivery of its own > wakework. I can re-test with something like that: diff --git a/kernel/cobalt/thread.c b/kernel/cobalt/thread.c index beda67e18..4c100b645 100644 --- a/kernel/cobalt/thread.c +++ b/kernel/cobalt/thread.c @@ -2159,6 +2159,7 @@ void xnthread_relax(int notify, int reason) pipeline_clear_mayday(); =20 trace_cobalt_shadow_relaxed(thread); + WARN_ON_ONCE(irq_work_is_busy(&wakework.inband_work.work)); } EXPORT_SYMBOL_GPL(xnthread_relax); But I fear this might take some time. The KASAM spat happened only once and also only after the test ran for almost 5 days. Thanks, //richard