linux-kernel - Re: [ANNOUNCE] Tools to analyse PM and scheduling behaviour

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-next>] [day] [month] [year] [list]

Message-ID: <20140813112234.GK9918@twins.programming.kicks-ass.net>
Date:	Wed, 13 Aug 2014 13:22:34 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Amit Kucheria <amit.kucheria@...aro.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux PM list <linux-pm@...r.kernel.org>,
	"Gross, Mark" <mark.gross@...el.com>,
	Paul McKenney <Paul.McKenney@...ibm.com>,
	Morten Rasmussen <Morten.Rasmussen@....com>,
	Dietmar Eggemann <Dietmar.Eggemann@....com>,
	Preeti U Murthy <preeti@...ux.vnet.ibm.com>,
	Daniel Lezcano <daniel.lezcano@...aro.org>,
	Vincent Guittot <vincent.guittot@...aro.org>,
	Mike Turquette <mturquette@...aro.org>,
	Juri Lelli <juri.lelli@....com>, sched-tools@...aro.org
Subject: Re: [ANNOUNCE] Tools to analyse PM and scheduling behaviour

On Fri, Aug 08, 2014 at 07:24:01PM +0530, Amit Kucheria wrote:
> Workload Generator Details
> --------------------------
> The Workload Generator is based on rt-app. Shared resources, waits, signals
> and locking order can be specified for each thread in a JSON description to
> construct complex interdependencies. This allows simulation of interesting
> use-cases. The repository contains examples of a mp3 and web-browsing
> workload.
> 
> The method to construct the JSON description is quite manual currently. We
> capture the trace of a workload of interest (say, on Android) and analyse
> it in kernelshark. We then construct the JSON description by hand until its
> resultant trace looks similar to the trace from the real workload.
> 
> The immediate goal is to expand the library to cover the common mobile
> workloads. We’re also working with the rt-app maintainer to get our changes
> merged.

With the end goal of having a program convert a trace into a JSON
description I take it?

Content of type "application/pgp-signature" skipped