* Ankita Garg <[EMAIL PROTECTED]> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
