Re: [PATCH v3 0/6] Static calls
From: H. Peter Anvin
Date: Sun Jan 13 2019 - 21:41:46 EST
On 1/13/19 6:31 PM, H. Peter Anvin wrote:
>
> static cpumask_t text_poke_cpumask;
>
> static void text_poke_sync(void)
> {
> smp_wmb();
> text_poke_cpumask = cpu_online_mask;
> smp_wmb(); /* Should be optional on x86 */
> cpumask_clear_cpu(&text_poke_cpumask, smp_processor_id());
> on_each_cpu_mask(&text_poke_cpumask, text_poke_sync_cpu, NULL, false);
> while (!cpumask_empty(&text_poke_cpumask)) {
> cpu_relax();
> smp_rmb();
> }
> }
>
> static void text_poke_sync_cpu(void *dummy)
> {
> (void)dummy;
>
> smp_rmb();
> cpumask_clear_cpu(&poke_bitmask, smp_processor_id());
> /*
> * We are guaranteed to return with an IRET, either from the
> * IPI or the #BP handler; this provides serialization.
> */
> }
>
The invariants here are:
1. The patching routine must set each bit in the cpumask after each event
that requires synchronization is complete.
2. The bit can be (atomically) cleared on the target CPU only, and only in a
place that guarantees a synchronizing event (e.g. IRET) before it may
reaching the poked instruction.
3. At a minimum the IPI handler and #BP handler needs to clear the bit. It
*is* also possible to clear it in other places, e.g. the NMI handler, if
necessary as long as condition 2 is satisfied.
-hpa