Re: [PATCH] Linux Kernel Markers 0.11 for 2.6.17

From: Jeremy Fitzhardinge
Date: Mon Sep 25 2006 - 17:22:35 EST

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.

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