On Wed, Dec 09, 2020 at 08:30:53AM +0100, Jürgen Groß wrote:
Hey, I already suggested to use ~FEATURE for that purpose (see
https://lore.kernel.org/lkml/f105a63d-6b51-3afb-83e0-e899ea40813e@xxxxxxxx/
Great minds think alike!
:-P
I'd rather make the syntax:
ALTERNATIVE_TERNARY <initial-code> <feature> <code-for-feature-set>
<code-for-feature-unset>
as this ...
Sure, that is ok too.
... would match perfectly to this interpretation.
Yap.
Hmm, using flags is an alternative (pun intended :-) ).
LOL!
Btw, pls do check how much the vmlinux size of an allyesconfig grows
with this as we will be adding a byte per patch site. Not that it would
matter too much - the flags are a long way a comin'. :-)
No, this is needed for non-Xen cases, too (especially pv spinlocks).
I see.
Can you give an example here pls why the paravirt patching needs to run
first?
Okay.
I meant an example for me to have a look at. :)
If possible pls.
Attachment:
OpenPGP_0xB0DE9DD628BF132F.asc
Description: application/pgp-keys
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature