From: Philippe Gerum <rpm@xenomai.org>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: xenomai@xenomai.org
Subject: Re: [PATCH 0/4] Dovetail fixes (v5.13)
Date: Tue, 03 Aug 2021 08:53:37 +0200 [thread overview]
Message-ID: <87eebb589a.fsf@xenomai.org> (raw)
In-Reply-To: <ccfa6190-ac98-7e6d-b7fa-6936c211e75e@siemens.com>
Hi Florian,
Florian Bezdeka via Xenomai <xenomai@xenomai.org> writes:
> Hi Philippe,
>
> On 31.07.21 11:49, Philippe Gerum via Xenomai wrote:
>> From: Philippe Gerum <rpm@xenomai.org>
>>
>> The usual pain with synchronizing the virtual and real interrupt
>> states. These issues have been detected while porting to v5.14, some
>> are reported by CONFIG_DEBUG_LOCKDEP=y.
>>
>
> One of our test boards (Intel XEON D) has an issue with the TSC being
> marked unstable because the clocksource watchdog is coming too late.
> Could one of these fixes explain that? Something like missed / dropped
> interrupts / interrupts not being delivered to Linux?
>
I don't think so, these fixes are not supposed to address this kind of
issue. They are merely aimed at keeping the interrupt state reported by
the IRQ flags tracer in sync with lockdep expectations. This series is
not complete yet, more is to come to fully address this matter and more.
Booting with CONFIG_DEBUG_LOCKDEP enabled, CONFIG_EVL/CONFIG_XENOMAI
disabled (i.e. only keeping the IRQ pipeline on) should reveal the
remaining problems. This also revealed a deeper and nastier issue than
de-synced IRQ flag tracing, particularly on ARM/arm64 where we do depend
on RCU read sides when traversing the interrupt pipeline, an unmet
dependency which is currently papered over as a result of having a
high-priority interrupt stage enabled in the kernel
(e.g. EVL/Xenomai). A fix is under test here.
--
Philippe.
prev parent reply other threads:[~2021-08-03 6:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 9:49 [PATCH 0/4] Dovetail fixes (v5.13) Philippe Gerum
2021-07-31 9:49 ` [PATCH 1/4] x86/ioapic: irq_pipeline: unbreak irqflags tracing Philippe Gerum
2021-07-31 9:49 ` [PATCH 2/4] init: early sync the inband stall with the hardware state Philippe Gerum
2021-07-31 9:49 ` [PATCH 3/4] x86/fault: dovetail: unbreak irqflags tracing Philippe Gerum
2021-07-31 9:49 ` [PATCH 4/4] genirq: irq_pipeline: fix inverted check in debug assertion Philippe Gerum
2021-08-02 19:12 ` [PATCH 0/4] Dovetail fixes (v5.13) Florian Bezdeka
2021-08-03 6:53 ` Philippe Gerum [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eebb589a.fsf@xenomai.org \
--to=rpm@xenomai.org \
--cc=florian.bezdeka@siemens.com \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.