|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v2 07/12] x86: add new features for paravirt patching
On 09.12.20 13:03, Borislav Petkov wrote: 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
Ah, okay.
Lets take the spin_unlock() case. With patch 11 of the series this is
PVOP_ALT_VCALLEE1(lock.queued_spin_unlock, lock,
"movb $0, (%%" _ASM_ARG1 ");",
X86_FEATURE_NO_PVUNLOCK);
which boils down to ALTERNATIVE "call *lock.queued_spin_unlock"
"movb $0,(%rdi)" X86_FEATURE_NO_PVUNLOCK
The initial (paravirt) code is an indirect call in order to allow
spin_unlock() before paravirt/alternative patching takes place.
Paravirt patching will then replace the indirect call with a direct call
to the correct unlock function. Then alternative patching might replace
the direct call to the bare metal unlock with a plain "movb $0,(%rdi)"
in case pvlocks are not enabled.
In case alternative patching would occur first, the indirect call might
be replaced with the "movb ...", and then paravirt patching would
clobber that with the direct call, resulting in the bare metal
optimization being removed again.
Juergen
Attachment:
OpenPGP_0xB0DE9DD628BF132F.asc Attachment:
OpenPGP_signature
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |