Re: [PATCH] Linux Kernel Markers 0.11 for 2.6.17

[Mathieu Desnoyers <compudj@krystal.dyndns.org>]

* Jeremy Fitzhardinge (jeremy@goop.org) 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!

Mathieu

OpenPGP public key:              http://krystal.dyndns.org:8080/key/compudj.gpg
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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/