/* SPDX-License-Identifier: GPL-2.0 */
#ifndef XEN_ALTERNATIVE_CALL
#define XEN_ALTERNATIVE_CALL

/*
 * Some subsystems in Xen may have multiple implementations, which can be
 * resolved to a single implementation at boot time.  By default, this will
 * result in the use of function pointers.
 *
 * Some architectures may have mechanisms for dynamically modifying .text.
 * Using this mechanism, function pointers can be converted to direct calls
 * which are typically more efficient at runtime.
 *
 * For architectures to support:
 *
 * - Implement alternative_{,v}call() in asm/alternative.h.  Code generation
 *   requirements are to emit a function pointer call at build time, and stash
 *   enough metadata to simplify the call at boot once the implementation has
 *   been resolved.
 * - Select ALTERNATIVE_CALL in Kconfig.
 *
 * To use:
 *
 * Consider the following simplified example.
 *
 *  1) struct foo_ops __alt_call_maybe_initdata ops;
 *
 *  2) const struct foo_ops __initconstrel foo_a_ops = { ... };
 *     const struct foo_ops __initconstrel foo_b_ops = { ... };
 *
 *     void __init foo_init(void)
 *     {
 *         ...
 *         if ( use_impl_a )
 *             ops = *foo_a_ops;
 *         else if ( use_impl_b )
 *             ops = *foo_b_ops;
 *         ...
 *     }
 *
 *  3) alternative_call(ops.bar, ...);
 *
 * There needs to a single ops object (1) which will eventually contain the
 * function pointers.  This should be populated in foo's init() function (2)
 * by one of the available implementations.  To call functions, use
 * alternative_{,v}call() referencing the main ops object (3).
 */

#ifdef CONFIG_ALTERNATIVE_CALL

#include <asm/alternative.h>

#define __alt_call_maybe_initdata __initdata

#else

#define alternative_call(func, args...)  (func)(args)
#define alternative_vcall(func, args...) (func)(args)

#define __alt_call_maybe_initdata __ro_after_init

#endif /* !CONFIG_ALTERNATIVE_CALL */
#endif /* XEN_ALTERNATIVE_CALL */
