mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Ankita Garg <ankita@in.ibm.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	linux@bohmer.net, LKML <linux-kernel@vger.kernel.org>,
	RT-Users <linux-rt-users@vger.kernel.org>,
	mathieu.desnoyers@polymtl.ca
Subject: Re: [Question] Hooks for scheduler tracing (CFS)
Date: Thu, 26 Jul 2007 09:53:53 +0200	[thread overview]
Message-ID: <20070726075353.GA19885@elte.hu> (raw)
In-Reply-To: <20070726074957.GA19398@in.ibm.com>


* Ankita Garg <ankita@in.ibm.com> wrote:

> > I'd suggest to not put a probe into a preempt-off section - put it 
> > to the beginning and to the end of schedule() to capture 
> > context-switches. _stp_print_flush() is in the systemtap-generated 
> > module, right? Maybe the problem is resolved by changing that 
> > spinlock to use raw_spinlock_t / DEFINE_RAW_SPIN_LOCK.
> 
> Yes, _stp_print_flush is in the systemtap-generated kprobe module. 
> Placing the probe at the beginning of schedule() also has the same 
> effect. Will try by changing the spinlock to raw_spinlock_t...

could you send us that module source ST generates? Perhaps there are 
preempt_disable() (or local_irq_disable()) calls in it too.

	Ingo

  reply	other threads:[~2007-07-26  7:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16 19:46 Remy Bohmer
2007-07-16 19:52 ` Arjan van de Ven
2007-07-16 20:17   ` Remy Bohmer
2007-07-16 21:12     ` Ingo Molnar
2007-07-26  7:28   ` Ankita Garg
2007-07-26  7:35     ` Ingo Molnar
2007-07-26  7:49       ` Ankita Garg
2007-07-26  7:53         ` Ingo Molnar [this message]
2007-07-26  9:59           ` Ankita Garg
2007-07-26 11:05             ` Ingo Molnar
2007-07-26 13:06               ` Mathieu Desnoyers
2007-07-26 17:45                 ` David J. Wilder
2007-07-26 18:30                   ` Mathieu Desnoyers
2007-07-26 13:20               ` Ankita Garg
2007-07-26 13:31     ` Mathieu Desnoyers
2007-07-26 14:47       ` Frank Ch. Eigler
2007-07-26 15:02         ` Mathieu Desnoyers
2007-07-26 16:22           ` Frank Ch. Eigler
2007-07-26 16:32             ` Ankita Garg
2007-07-26 18:25             ` Mathieu Desnoyers
2007-07-26 15:17         ` Arnaldo Carvalho de Melo
2007-07-16 20:07 ` Mathieu Desnoyers
2007-07-16 23:03 ` LTTng for 2.6.22.1-rt4 Mathieu Desnoyers
     [not found]   ` <3efb10970707170034t3e1dabe5wc70d41f6ab209c7e@mail.gmail.com>
2007-07-17 14:45     ` LTTng for 2.6.22.1-rt4 (timestamping) Mathieu Desnoyers
2007-07-17  7:23 ` [Question] Hooks for scheduler tracing (CFS) Sébastien Dugué

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=20070726075353.GA19885@elte.hu \
    --to=mingo@elte.hu \
    --cc=ankita@in.ibm.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=linux@bohmer.net \
    --cc=mathieu.desnoyers@polymtl.ca \
    /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®