From: Jens Axboe <axboe@kernel.dk>
To: Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Wander Lairson Costa <wander@redhat.com>,
"open list:BLOCK LAYER" <linux-block@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH v5 1/1] blktrace: switch trace spinlock to a raw spinlock
Date: Mon, 20 Dec 2021 13:50:53 -0700 [thread overview]
Message-ID: <164003345302.532019.10882095301451527257.b4-ty@kernel.dk> (raw)
In-Reply-To: <20211220192827.38297-1-wander@redhat.com>
On Mon, 20 Dec 2021 16:28:27 -0300, Wander Lairson Costa wrote:
> The running_trace_lock protects running_trace_list and is acquired
> within the tracepoint which implies disabled preemption. The spinlock_t
> typed lock can not be acquired with disabled preemption on PREEMPT_RT
> because it becomes a sleeping lock.
> The runtime of the tracepoint depends on the number of entries in
> running_trace_list and has no limit. The blk-tracer is considered debug
> code and higher latencies here are okay.
>
> [...]
Applied, thanks!
[1/1] blktrace: switch trace spinlock to a raw spinlock
commit: 361c81dbc58c8aa230e1f2d556045fa7bc3eb4a3
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2021-12-20 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 19:28 Wander Lairson Costa
2021-12-20 19:38 ` Jens Axboe
2021-12-20 19:49 ` Wander Costa
2021-12-20 20:24 ` Jens Axboe
2021-12-20 20:34 ` Wander Costa
2021-12-20 20:37 ` Jens Axboe
2021-12-20 20:43 ` Wander Costa
2021-12-20 20:49 ` Jens Axboe
2021-12-20 23:30 ` Steven Rostedt
2021-12-20 23:45 ` Jens Axboe
2021-12-20 20:50 ` Jens Axboe [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=164003345302.532019.10882095301451527257.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wander@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
all inboxes | Powered by JetHome®