lkml.org 
[lkml]   [2021]   [Jan]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 1/2] KVM: x86: introduce definitions to support static calls for kvm_x86_ops
    On Wed, Jan 13, 2021, Jason Baron wrote:
    >
    > On 1/13/21 7:53 AM, Paolo Bonzini wrote:
    > > #define KVM_X86_OP(func) \
    > >   static_call_update(kvm_x86_##func, kvm_x86_ops.func)
    > > #define KVM_X86_OP_NULL(func) \
    > >   static_call_update(kvm_x86_##func, kvm_x86_ops.func)
    > > #include <asm/kvm-x86-ops.h>
    > >
    > > In that case vmx.c and svm.c could define KVM_X86_OP_NULL to an empty
    > > string and list the optional callbacks manually.
    > >
    >
    > Ok, yes, this all makes sense. So I looked at vmx/svm definitions
    > and I see that there are 5 definitions that are common that
    > don't use the vmx or svm prefix:

    We'll rename the helpers when doing the conversion, i.e. you can safely assume
    that all VMX/SVM functions will use the pattern {vmx,svm}_##func. I did all the
    renaming a few months back, but it got tossed away when svm.c was broken up.

    > .update_exception_bitmap = update_exception_bitmap,
    > .enable_nmi_window = enable_nmi_window,
    > .enable_irq_window = enable_irq_window,
    > .update_cr8_intercept = update_cr8_intercept,
    > .enable_smi_window = enable_smi_window,

    \
     
     \ /
      Last update: 2021-01-13 18:14    [W:4.068 / U:1.748 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site