lkml.org 
[lkml]   [2020]   [Dec]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH v2 07/12] x86: add new features for paravirt patching
    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@suse.com/

    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.

    Thx.

    --
    Regards/Gruss,
    Boris.

    https://people.kernel.org/tglx/notes-about-netiquette

    \
     
     \ /
      Last update: 2020-12-09 13:05    [W:2.414 / U:0.088 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site