> Probing vmalloc faults is _really_ tricky : it also implies that the > handler (let's call it probe) connected to the probe point (marker or > kprobe) should _never_ cause a vmalloc page fault,
That is why vmalloc_sync_all() was invented. It might make sense to just call that on kprobe registration. But I agree the other problems makes it a bad idea. I think the better solution is to keep the notifier, but make it cheaper (e.g. by using constant patching ...) -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/
