Self modifying code in ARM 11 architectures

[Mulyadi Santosa]

Hi Michi...

On Wed, May 25, 2011 at 22:18, Michael Blizek
<michi1 at michaelblizek.twilightparadox.com> wrote:
> This sounds like a very interesting arch to me. I would very much like to see
> any code which does cache flushing when changing a function pointer. In the
> mean time, let us assume that function pointers are data, not code. ;-) Then,
> you still have to think about concurrency, but not about cache flushing.

I think, changing function pointer assignment is only needed in SMP
environment and when we see a chance that that code is executed by
more than one concurrent code path. Other than that, in x86, i think
it's not needed. And thanks for x86 strict memory ordering, we're not
burdened with too much memory barrier.

CMIIW here people...

-- 
regards,

Mulyadi Santosa
Freelance Linux trainer and consultant

blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com