Skip to contentSkip to conversation

LTTng-core (basic tracing infrastructure) 0.5.108]

PATCH Frank Ch. Eigler 2 participants 2 messages Sep 15, 2006

lore
Share & tools
lore
#0 lore raw

Hi -

Quoted 1 line · Alan Cox

Ar Gwe, 2006-09-15 am 13:08 -0400, ysgrifennodd Frank Ch. Eigler:

Yeah, or something. :-)

Quoted 5 lines
Quoted 2 lines

Alan Cox <[email protected]> writes:
- where 1000-cycle int3-dispatching overheads too high

Why are your despatching overheads 1000 cycles ? (and if its due to int3 why are you using int 3 8))

Smart teams from IBM and Hitachi have been hammering away at this code for a year or two now, and yet (roughly) here we are. There have been experiments involving plopping branches instead of int3's at probe locations, but this is self-modifying code involving multiple instructions, and appears to be tricky on SMP/preempt boxes.

- FChE

#1 lore raw

Ar Gwe, 2006-09-15 am 14:34 -0400, ysgrifennodd Frank Ch. Eigler:

Quoted 2 lines

locations, but this is self-modifying code involving multiple instructions, and appears to be tricky on SMP/preempt boxes.

Can you explain more about why this is the case. I would have though that it's the same with one instruction or 100 to the non SMP case. You may never patch an instruction while another CPU may be executing that path and there must be a synchronizing point for each CPU before it hits the patched instruction. See the Intel and AMD chip errata documents.

Figuring out how long to patch is a more complicated problem but there is extant code to compute the length of an x86 instruction.

Alan