On Wednesday 31 August 2005 01:54, Christoph Lameter wrote: > Certainly not a big effect (if we make sure the compiler knows that > this test mostly fails and insure that the variable is in > __mostly_read)
Currently neither, but that could be easily fixed. > but this is a frequently executed code path and the code > is there without purpose if CONFIG_KPROBES is off. Well if you really worry about it then it might be better to do some dynamic code patching to make generic and distribution kernels too. > It wont get too bad unless lots of other people have similar ideas about > fixing their race conditions using similar methods. But we will be setting > a bad precedent if we allow this. Agreed on the general direction, but I didn't see an alternative for kprobes for this. Well actually the hook could be maybe right now moved into the part before kernel oops which is much less frequently executed, but then it'll likely move up again once kprobes support user space probes. -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
