Re: [PATCH] Linux Kernel Markers 0.11 for 2.6.17

From: Mathieu Desnoyers
Date: Mon Sep 25 2006 - 17:37:44 EST

* Jeremy Fitzhardinge (jeremy@xxxxxxxx) wrote:
> Mathieu Desnoyers wrote:
> >Better idea : we could put a read/write dependency on a memory location.
> >
> Yes, that works well. And it needn't even exist:
> extern int __marker_sequencer; /* doesn't exist, never
> referenced */
> asm volatile("first asm" : "+m" (__marker_sequencer));
> asm volatile("second asm" : "+m" (__marker_sequencer));
> This keeps the asms ordered with respect to each other (and prevents to
> independent markers from being intermingled), but it doesn't prevent
> them from being re-ordered with respect to other code.
I will declare the pointers around the jmp instruction directly in assembly : I
wouldn't want gcc to put some other code there by mistake.

I will use the "name" variable, as it is already there.

A new version coming soon...

Thank you very much!


OpenPGP public key:
Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at