From mboxrd@z Thu Jan 1 00:00:00 1970 From: mulyadi.santosa@gmail.com (Mulyadi Santosa) Date: Wed, 25 May 2011 22:55:16 +0700 Subject: Self modifying code in ARM 11 architectures In-Reply-To: <20110525151848.GA2085@michaelblizek.twilightparadox.com> References: <20110525151848.GA2085@michaelblizek.twilightparadox.com> Message-ID: To: kernelnewbies@lists.kernelnewbies.org List-Id: kernelnewbies.lists.kernelnewbies.org Hi Michi... On Wed, May 25, 2011 at 22:18, Michael Blizek 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