All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Wragg <david@wragg.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Albert Cahalan <acahalan@gmail.com>,
	linux-kernel@vger.kernel.org, bcrl@kvack.org
Subject: Re: [PATCH] procfs: export context switch counts in /proc/*/stat
Date: Wed, 20 Dec 2006 14:38:06 +0000	[thread overview]
Message-ID: <871wmuab01.fsf@wragg.org> (raw)
In-Reply-To: <1166622487.3365.1386.camel@laptopd505.fenrus.org> (Arjan van de Ven's message of "Wed\, 20 Dec 2006 14\:48\:06 +0100")

Arjan van de Ven <arjan@infradead.org> writes:
> if all you care is the number of context switches, you can use the
> following system tap script as well:
>
> http://www.fenrus.org/cstop.stp

Thanks, something similar to that might well have solved my original
problem.  

(When I try the script, stap complains about the lack of the kernel
debuginfo package, which of course doesn't exist for my self-built
kernel.  After hunting around on the web for 10 minutes, I'm still no
closer to resolving this.  But I look forward to playing with
systemtap once I get past that problem.)

Nonetheless, while systemtap might provide an objection to adding
per-task context switch counters to the kernel, it doesn't answer the
question, since we do have these counters, why not expose them in the
normal way?


David

  reply	other threads:[~2006-12-20 14:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20  5:40 [PATCH] procfs: export context switch counts in /proc/*/stat Albert Cahalan
2006-12-20 13:20 ` David Wragg
2006-12-20 13:48   ` Arjan van de Ven
2006-12-20 14:38     ` David Wragg [this message]
2006-12-20 14:51       ` Arjan van de Ven
2006-12-20 15:13         ` David Wragg
2006-12-20 17:36   ` Albert Cahalan
2006-12-24  1:40     ` David Wragg
  -- strict thread matches above, loose matches on Subject: below --
2006-12-21  6:02 Al Boldi
2006-12-18 23:50 David Wragg
2006-12-19  6:39 ` Benjamin LaHaise
2006-12-19 11:47   ` David Wragg

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=871wmuab01.fsf@wragg.org \
    --to=david@wragg.org \
    --cc=acahalan@gmail.com \
    --cc=arjan@infradead.org \
    --cc=bcrl@kvack.org \
    --cc=linux-kernel@vger.kernel.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 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.