Re: [I-pipe 4.4] [PATCH v2 1/4] ipipe: x86: Do not call BUG() in case of retriggered APIC vectors

2022-03-01 Thread Florian Bezdeka via Xenomai
On 01.03.22 21:21, Jan Kiszka wrote: > On 01.03.22 13:52, Florian Bezdeka wrote: >> The CPU hotplugging code might re-trigger a vector. In that case the >> vector is in the VECTOR_RETRIGGERED state. With this patch applied ipipe >> does no longer call BUG() for such vectors. >> > > Doesn't this

Re: [I-pipe 4.4] [PATCH v2 1/4] ipipe: x86: Do not call BUG() in case of retriggered APIC vectors

2022-03-01 Thread Jan Kiszka via Xenomai
On 01.03.22 13:52, Florian Bezdeka wrote: > The CPU hotplugging code might re-trigger a vector. In that case the > vector is in the VECTOR_RETRIGGERED state. With this patch applied ipipe > does no longer call BUG() for such vectors. > Doesn't this also avoids a BUG for spurious vectors

[I-pipe 4.4] [PATCH v2 1/4] ipipe: x86: Do not call BUG() in case of retriggered APIC vectors

2022-03-01 Thread Florian Bezdeka via Xenomai
The CPU hotplugging code might re-trigger a vector. In that case the vector is in the VECTOR_RETRIGGERED state. With this patch applied ipipe does no longer call BUG() for such vectors. This is a backport from the 4.19 and 5.4 ipipe branches handling the VECTOR_SHUTDOWN state. The VECTOR_SHUTDOWN