All of lore.kernel.org
 help / color / mirror / Atom feed
From: Morten Rasmussen <Morten.Rasmussen@arm.com>
To: Dhaval Giani <dhaval.giani@gmail.com>
Cc: Paul Turner <pjt@google.com>, Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <peterz@infradead.org>,
	Paul McKenney <paulmck@linux.vnet.ibm.com>,
	Benjamin Segall <bsegall@google.com>,
	Ranjit Manomohan <ranjitm@google.com>,
	Nikhil Rao <ncrao@google.com>, "jmc@cs.unc.edu" <jmc@cs.unc.edu>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Srivatsa Vaddagiri <vatsa@in.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Abhishek Srivastava <a.srivastava.800@gmail.com>
Subject: Re: [ANNOUNCE] LinSched for v3.3-rc7
Date: Wed, 21 Mar 2012 14:20:27 +0000	[thread overview]
Message-ID: <20120321142026.GA29148@e103034-lin.cambridge.arm.com> (raw)
In-Reply-To: <CAPhKKr-W+nh9Xzmwz83MUpzPuBfkj_TxjiZ+8NA5hndDUQB7bA@mail.gmail.com>

Hi,

On Thu, Mar 15, 2012 at 04:08:17AM +0000, Dhaval Giani wrote:
> [Adding abhishek to the cc]
> 
> On Wed, Mar 14, 2012 at 8:58 PM, Paul Turner <pjt@google.com> wrote:
> > - Support for record and replay of application scheduling via perf.
> > This is not yet well integrated, but under tests exist the tools to
> > record an applications behavior using perf sched record, and then play
> > it back in the simulator.

I am interested in testing this feature and I could use a hint on how to
get it working. tests/perf_replay.c seems to accept perf sched record
traces which have been post-processed into .rlog traces. Where can I
find a tool to generate rlogs from perf traces?

Thanks,
Morten


  parent reply	other threads:[~2012-03-21 14:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15  3:58 [ANNOUNCE] LinSched for v3.3-rc7 Paul Turner
2012-03-15  4:08 ` Dhaval Giani
2012-03-21  9:20   ` Michael Wang
2012-03-21  9:54     ` Paul Turner
2012-03-21 10:11       ` Michael Wang
2012-03-21 14:20   ` Morten Rasmussen [this message]
2012-03-15  7:21 ` Ingo Molnar
2012-03-23  4:03 ` Michael Wang
2012-03-28  5:19   ` Michael Wang
2012-04-09  3:29 ` Michael Wang
2012-07-23  3:03 ` Michael Wang
2012-07-23 12:54   ` Paul Turner

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=20120321142026.GA29148@e103034-lin.cambridge.arm.com \
    --to=morten.rasmussen@arm.com \
    --cc=a.srivastava.800@gmail.com \
    --cc=bsegall@google.com \
    --cc=dhaval.giani@gmail.com \
    --cc=jmc@cs.unc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=ncrao@google.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=ranjitm@google.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=vatsa@in.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.