* Daniel Walker <[EMAIL PROTECTED]> wrote:
> On Tue, 2007-04-24 at 13:24 -0700, Jeremy Fitzhardinge wrote:
>
> > And sched_clock's use of local_irq_save/restore appears to be absolutely
> > correct, so I think it must be triggering a bug in either the self-tests
> > or lockdep itself.
>
> Why does sched_clock need to disable interrupts?
i concur. To me it appears not "absolutely correct" that someone
apparently added local_irq_save/restore to sched_clock(), but "absolute
madness". sched_clock() is _very_ performance-sensitive for the
scheduler, do not mess with it.
Ingo
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/virtualization
