From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Carsten Emde <C.Emde@osadl.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH] Make output of RT throttling more verbose
Date: Mon, 22 Aug 2016 09:40:06 +0200 [thread overview]
Message-ID: <20160822074005.ecckrxmnnqy72crs@linutronix.de> (raw)
In-Reply-To: <250cd9a5-7b1d-96b4-1317-c54bc632bb6a@osadl.org>
On 2016-08-21 23:39:21 [+0200], Carsten Emde wrote:
> Hi Sebastian,
Hi Carsten,
> We could save a short history of RT tasks along with their uninterrupted
> runtime and, in case of throttling, print the one with the longest
> uninterrupted runtime.
A sched_switch tracer would do that. It only does not stop and records
SCHED_OTHER as well. Maybe the tracing folks have an idea.
> Carsten.
Sebastian
prev parent reply other threads:[~2016-08-22 7:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-14 0:12 [PATCH] Make output of RT throttling more verbose Carsten Emde
2016-08-17 8:46 ` Sebastian Andrzej Siewior
2016-08-21 21:39 ` Carsten Emde
2016-08-22 7:40 ` 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=20160822074005.ecckrxmnnqy72crs@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=C.Emde@osadl.org \
--cc=linux-rt-users@vger.kernel.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 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).