From: Amit Kucheria <amit.kucheria@linaro.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>, "Gross\,
Mark" <mark.gross@intel.com>,
Paul McKenney <Paul.McKenney@us.ibm.com>,
Morten Rasmussen <Morten.Rasmussen@arm.com>,
Dietmar Eggemann <Dietmar.Eggemann@arm.com>,
Preeti U Murthy <preeti@linux.vnet.ibm.com>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Mike Turquette <mturquette@linaro.org>,
Juri Lelli <juri.lelli@arm.com>,
sched-tools@linaro.org
Subject: Re: [ANNOUNCE] Tools to analyse PM and scheduling behaviour
Date: Thu, 14 Aug 2014 00:11:13 +0530 [thread overview]
Message-ID: <8761hwcjw6.fsf@matterhorn.verdurent.com> (raw)
In-Reply-To: <20140813112234.GK9918@twins.programming.kicks-ass.net>
Peter Zijlstra <peterz@infradead.org> writes:
> 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?
Either that or re-evaluate if perf record and playback can actually do
away with the need to do this.
prev parent reply other threads:[~2014-08-13 18:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP245DUSAHO_VBoBMy4KQaaA6_0a-i3Y3u4utnK8ji3UMVniyA@mail.gmail.com>
2014-08-13 11:22 ` Peter Zijlstra
2014-08-13 18:41 ` Amit Kucheria [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=8761hwcjw6.fsf@matterhorn.verdurent.com \
--to=amit.kucheria@linaro.org \
--cc=Dietmar.Eggemann@arm.com \
--cc=Morten.Rasmussen@arm.com \
--cc=Paul.McKenney@us.ibm.com \
--cc=daniel.lezcano@linaro.org \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=mingo@kernel.org \
--cc=mturquette@linaro.org \
--cc=peterz@infradead.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=rjw@rjwysocki.net \
--cc=sched-tools@linaro.org \
--cc=vincent.guittot@linaro.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
all inboxes | Powered by JetHome®