Sunday, 11 July 2010

dtrace progress 20100711

I've been fixing dtrace to run on the 2.6.32 kernel (hopefully
fixes are applicable to 2.6.33 - but time will tell).

Theres two major bugs at present:

  1. The first is that the hrtimer is causing issues; I think I know why
    and have put in an interim fix. This seems to be stopping the general
    panics caused by interrupts being disabled in an interrupt routine
    (local_irq_disable() called from hrtimer callback)

  2. The second is more awful; the assembler glue to launch syscalls
    changed somewhere from 2.6.30 -> 2.6.32, and now a few syscalls
    will panic the kernel, e.g. "clone" (called by fork()). I nearly
    understand why, but its a mess having to support lots of kernels
    and the 32+64 bit variants.
    For now,

    $ dtrace -n syscall::[d-z]*:

    works but not:

    $ dtrace -n syscall:::

Not sure when I will fix these - maybe this week or maybe in august,
so keep checking back.

Post created by CRiSP v10.0.2a-b5877

No comments:

Post a Comment