On Thu, Nov 17, 2022 at 04:42:57PM +0000, Sean Christopherson wrote: > Why? This is rarely run code, won't cpu_feature_enabled() > unnecessarily require patching? Because we want one single interface to test X86_FEATURE flags. And there's no need for the users to know whether it wants patching or not - we simply patch *everywhere* and that's it. > And while we're on the topic... https://lore.kernel.org/all/Y22IzA9DN%2FxYWgWN@xxxxxxxxxx Because static_ or boot_ is not relevant to the user - all she wants to know is whether a cpu feature has been enabled. Thus cpu_feature_enabled(). And yes, at the time I protested a little about unnecessary patching. And tglx said "Why not?". And I had no good answer to that. So we can just as well patch *everywhere*. And patching is soo not a big deal anymore considering all the other things we do to kernel code at build time and runtime. objdump output compared to what's actually running has in some cases no resemblance whatsoever. Thx. -- Regards/Gruss, Boris. https://people.kernel.org/tglx/notes-about-netiquette
