From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: John Ogness <john.ogness@linutronix.de>,
Pierre Gondois <pierre.gondois@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [ANNOUNCE] v6.3-rc2-rt3
Date: Tue, 18 Apr 2023 17:08:28 +0200 [thread overview]
Message-ID: <20230418150828.tNv46UyK@linutronix.de> (raw)
In-Reply-To: <c49c2984-10a3-de8e-c12b-9a3833270a11@suse.cz>
On 2023-04-14 17:38:56 [+0200], Vlastimil Babka wrote:
> What I meant that in the linked thread a solution seems to be forming in the
> form of annotation for lockdep/CONFIG_PROVE_RAW_LOCK_NESTING to make it
> aware that on CONFIG_PREEMPT_RT the problem it sees is side-stepped so it
> shouldn't warn about it on !PREEMPT_RT, and maybe that solution could be
> used for the printk issue as well (I admit I didn't check the code, just by
> reading your mail it sounded very similar).
Yes, you right and it would work and I would include it. Once the
DEBUG_OBJECT part is merged (the LD_LOCK_WAIT logic is missing) I would
add something here.
Sebastian
prev parent reply other threads:[~2023-04-18 15:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 17:05 [ANNOUNCE] v6.3-rc2-rt3 Sebastian Andrzej Siewior
2023-03-14 17:12 ` Sebastian Andrzej Siewior
2023-04-14 11:55 ` Pierre Gondois
2023-04-14 13:49 ` John Ogness
2023-04-14 13:56 ` Vlastimil Babka
2023-04-14 15:01 ` John Ogness
2023-04-14 15:38 ` Vlastimil Babka
2023-04-18 15:08 ` Sebastian Andrzej Siewior [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=20230418150828.tNv46UyK@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pierre.gondois@arm.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
/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.