All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Li Zhong <zhong@linux.vnet.ibm.com>,
	Borislav Petkov <bp@alien8.de>,
	Christoph Lameter <cl@linux-foundation.org>,
	Kevin Hilman <khilman@linaro.org>,
	Mats Liljegren <liljegren.mats2@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] Full dynticks selftests 0.0.1
Date: Wed, 12 Jun 2013 17:19:17 +0200	[thread overview]
Message-ID: <20130612151915.GD5332@somewhere> (raw)

Hi all,

I've been using a homemade test for full dynticks all that time and I regret I haven't shared
it much sooner. I've been asked for such a tool many times and getting full dynticks working
correctly is often not a piece of cake.

Here it is, a very basic test that runs a userspace loop for ten seconds and dumps a trace
of the tick, scheduler, workqueue, and other kind of kernel noise.

You can fetch from:

git://git.kernel.org/pub/scm/linux/kernel/git/frederic/dynticks-testing.git
	master

I hope it helps! Feel free to send any kind of improvements if you wish.

Thanks!

             reply	other threads:[~2013-06-12 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 15:19 Frederic Weisbecker [this message]
2013-06-18 14:20 ` [ANNOUNCE] Full dynticks selftests 0.0.1 Christoph Lameter
2013-06-18 15:15   ` Paul E. McKenney
2013-06-18 16:22     ` Frederic Weisbecker
2013-06-18 18:17       ` Paul E. McKenney
2013-06-19 14:19         ` Christoph Lameter
2013-06-19 15:38         ` Frederic Weisbecker

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=20130612151915.GD5332@somewhere \
    --to=fweisbec@gmail.com \
    --cc=bp@alien8.de \
    --cc=cl@linux-foundation.org \
    --cc=khilman@linaro.org \
    --cc=liljegren.mats2@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=zhong@linux.vnet.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.