On 02.09.20 11:12, 孙世龙 sunshilong wrote:
> Hi,
>
>> That is a (reasonable) design decision because you would otherwise risk
>> that a handler registered for low-prio task can block the delivery of an
>> event for a high-prio task. I would just be a mess, at least in a more
>> complex RT
Hi,
>That is a (reasonable) design decision because you would otherwise risk
>that a handler registered for low-prio task can block the delivery of an
>event for a high-prio task. I would just be a mess, at least in a more
>complex RT application.
I see, thank you for the clarification.
It
On 01.09.20 11:11, 孙世龙 sunshilong via Xenomai wrote:
> Hi,
>
> I found that the timer-internal thread is set with the
> THREADOBJ_IRQCONTEXT flag.
> Here is the related code snippet:
> static int server_prologue(void *arg)
> {
>svpid = get_thread_pid();
>
Hi,
I found that the timer-internal thread is set with the
THREADOBJ_IRQCONTEXT flag.
Here is the related code snippet:
static int server_prologue(void *arg)
{
svpid = get_thread_pid();
copperplate_set_current_name("timer-internal");
timersv_init_corespec();
