From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
tglx@linutronix.de, Clark Williams <williams@redhat.com>,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: cgroup trace events acquire sleeping locks
Date: Tue, 10 Jul 2018 09:32:45 -0400 [thread overview]
Message-ID: <20180710093245.4e326156@gandalf.local.home> (raw)
In-Reply-To: <20180710092635.GD2476@hirez.programming.kicks-ass.net>
On Tue, 10 Jul 2018 11:26:35 +0200
Peter Zijlstra <peterz@infradead.org> wrote:
> > Hmm, good question. I could possibly make all the tracepoint code into
> > its own section. And then look to see if any spin locks exist in them.
> > That wouldn't be too trivial to implement though.
>
> pick a bit from the preempt_count (say right above NMI_MASK) and set it
> inside a trace-event and add in_trace().
>
> Then make lockdep explode when in_trace().
>
> Or something along those lines.
Sure. We have current->trace for special tracing flags. That could
easily be used.
-- Steve
prev parent reply other threads:[~2018-07-10 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180703140750.1dab75ef@tagon>
[not found] ` <20180706174745.hwvnwojzfbmp7ma5@linutronix.de>
[not found] ` <20180708203600.2edf24e2@tagon>
2018-07-09 16:38 ` cgroup trace events acquire sleeping locks Sebastian Andrzej Siewior
2018-07-09 19:01 ` Steven Rostedt
2018-07-09 20:22 ` Sebastian Andrzej Siewior
2018-07-09 20:30 ` Steven Rostedt
2018-07-10 9:26 ` Peter Zijlstra
2018-07-10 13:32 ` Steven Rostedt [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=20180710093245.4e326156@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).