On Thu, 11 Jul 2013, Jiri Kosina wrote: > > Returning to the instruction will, in effect, be a busy-wait for the > > faulted CPU until the patch is complete; more or less what stop_machine > > would do, but only for a CPU which actually strays into the affected > > region. > > To be honest, I fail to see a clear advantage ... we don't avoid any extra > IPI by it, and wrt. "correctness", the end result is the same.
Ok, after some offline discussion, my understanding is that with this proposal you are willing to make this usable in a more general way than just simple nop -> jump -> nop patching. That makes sense, but I'd propose to have a different independent interface for this if needed (text_poke_bp_busy() ... ?) in parallel to the text_poke_bp() as is in my patchset, due to the obvious extra cycles it's bringing. Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
