References: <5185508f-d8b7-fb49-de71-65c70eb33f8a@siemens.com> <7daf0026-aab0-0d32-b52f-3f5ce993a7ac@siemens.com> <87r1ftqeaq.fsf@xenomai.org> From: Philippe Gerum Subject: Re: [PATCH v2 0/3] Add callback-like mechanism before/after ptrace stops In-reply-to: <87r1ftqeaq.fsf@xenomai.org> Date: Tue, 20 Jul 2021 16:08:43 +0200 Message-ID: <87k0llqdqs.fsf@xenomai.org> MIME-Version: 1.0 Content-Type: text/plain List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Richard Weinberger Cc: Jan Kiszka , xenomai@xenomai.org Philippe Gerum writes: > Richard Weinberger via Xenomai writes: > >> On Tue, Jul 20, 2021 at 12:53 PM Jan Kiszka wrote: >>> > I've heard that with dovetail Xenomai no longer sees exceptions. >>> > So this is a set in stone concept? >>> >>> Xenomai can no longer declare exceptions resolved. It still sees them. >> >> Understood. >> >>> If we come up with a reasonable use case, I can't imagine that this is >>> set in stone. >> >> I can understand that dovetail doesn't want to offer something super generic >> as ipipe_trap_hook(). > > Just like the I-pipe, Dovetail implements a way to tell the companion > core that "something happened", including a fault for the current task, > by calling handlers with weak bindings the core can > override. For faults, this would be oob_trap_notify(). oob_trap_notify() is a Dovetail service calling the following weak hooks which should be provided by the core actually: handle_oob_trap_entry() then handle_oob_trap_exit(). -- Philippe.