This is the mail archive of the systemtap@sources.redhat.com mailing list for the systemtap project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
[...] Can you outline what these are for?
Some of the LKST_ operations are for management of LKST. There events are listed in lkst-events-2.1.pdf. [...]
[...]
I guess I don't understand what "management of LKST" means.
[...] It would be nice if the probe could be [placed] inside the spinlock region of the instrumented code. This would ensure that data is gathered and minimize perturbations by attempting to get the lock twice.
That's true. In case it's not clear though, sometimes we may have to traverse a lock-protected data structure from a routine that is not involved directly with it, like a timer interrupt. It is possible not lock these data structures from within a probe that's traversing them, but that of course risks reading junk data on SMP.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |