linux-kernel - Re: [RFC][PATCH 4/4] sched: Add debugfs/sched/deadline

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160201173809.3df5c1f3@gandalf.local.home>
Date:	Mon, 1 Feb 2016 17:38:09 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Juri Lelli <juri.lelli@...il.com>,
	Clark Williams <williams@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC][PATCH 4/4] sched: Add debugfs/sched/deadline_bw file to
 show current bandwidths

On Mon, 1 Feb 2016 23:17:20 +0100
Peter Zijlstra <peterz@...radead.org> wrote:

> On Mon, Feb 01, 2016 at 03:26:28PM -0500, Steven Rostedt wrote:
> > From: "Steven Rostedt (Red Hat)" <rostedt@...dmis.org>
> > 
> > Add a /sys/kernel/debug/sched directory and place a deadline_bw file there
> > that shows the current bandwidths of the CPUs for SCHED_DEADLINE tasks.
> > 
> >   # cat /sys/kernel/debug/sched/deadline_bw
> >   CPU[0]:
> >     bw:       996147
> >     total_bw: 0
> >   CPU[1]:
> >     bw:       996147
> >     total_bw: 0
> >   CPU[2]:
> >     bw:       996147
> >     total_bw: 0
> >   CPU[3]:
> >     bw:       996147
> >     total_bw: 0
> >   CPU[4]:
> >     bw:       996147
> >     total_bw: 0
> >   CPU[5]:
> >     bw:       996147
> >     total_bw: 0
> >   CPU[6]:
> >     bw:       996147
> >     total_bw: 0
> >   CPU[7]:
> >     bw:       996147
> >     total_bw: 0  
> 
> Why not add this to print_dl_rq() ?

Because I didn't see that ;-)

That could work, although, Damn there's a lot of info there already.
I'll play with that.

Regardless of this final patch, what do you think of the first three? I
can send them as a separate series, just to get more of the SCHED_DEBUG
code into debug.c.

-- Steve