For the !CONFIG_ALTERNATIVE_CALL case, the use of __read_mostly was only a stopgap while nothing better existed. __ro_after_init now does, so it use.
Signed-off-by: Andrew Cooper <andrew.coop...@citrix.com> --- CC: Jan Beulich <jbeul...@suse.com> CC: Roger Pau Monné <roger....@citrix.com> CC: Wei Liu <w...@xen.org> v2: * New --- xen/include/xen/alternative-call.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xen/include/xen/alternative-call.h b/xen/include/xen/alternative-call.h index c2d3b70e312e..5c6b9a562b92 100644 --- a/xen/include/xen/alternative-call.h +++ b/xen/include/xen/alternative-call.h @@ -57,7 +57,7 @@ #define alternative_call(func, args...) (func)(args) #define alternative_vcall(func, args...) (func)(args) -#define __alt_call_maybe_initdata __read_mostly +#define __alt_call_maybe_initdata __ro_after_init #endif /* !CONFIG_ALTERNATIVE_CALL */ #endif /* XEN_ALTERNATIVE_CALL */ -- 2.11.0
