<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>ea4290d7 - KVM: x86: leave kvm.ko out of the build if no vendor module is requested</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#ea4290d7</link>
        <description>KVM: x86: leave kvm.ko out of the build if no vendor module is requestedkvm.ko is nothing but library code shared by kvm-intel.ko and kvm-amd.ko.It provides no functionality on its own and it is unnecessary unless oneof the vendor-specific module is compiled.  In particular, /dev/kvm isnot created until one of kvm-intel.ko or kvm-amd.ko is loaded.Use CONFIG_KVM to decide if it is built-in or a module, but use thevendor-specific modules for the actual decision on whether to build it.This also fixes a build failure when CONFIG_KVM_INTEL and CONFIG_KVM_AMDare both disabled.  The cpu_emergency_register_virt_callback() functionis called from kvm.ko, but it is only defined if at least one ofCONFIG_KVM_INTEL and CONFIG_KVM_AMD is provided.Fixes: 590b09b1d88e (&quot;KVM: x86: Register &quot;emergency disable&quot; callbacks when virt is enabled&quot;)Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Tue, 01 Oct 2024 14:15:01 +0000</pubDate>
        <dc:creator>Paolo Bonzini &lt;pbonzini@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>5f18c642 - KVM: VMX: Move out vmx_x86_ops to &apos;main.c&apos; to dispatch VMX and TDX</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#5f18c642</link>
        <description>KVM: VMX: Move out vmx_x86_ops to &apos;main.c&apos; to dispatch VMX and TDXKVM accesses Virtual Machine Control Structure (VMCS) with VMX instructionsto operate on VM.  TDX doesn&apos;t allow VMM to operate VMCS directly.Instead, TDX has its own data structures, and TDX SEAMCALL APIs for VMM toindirectly operate those data structures.  This means we must have a TDXversion of kvm_x86_ops.The existing global struct kvm_x86_ops already defines an interface whichcan be adapted to TDX, but kvm_x86_ops is a system-wide, not per-VMstructure.  To allow VMX to coexist with TDs, the kvm_x86_ops callbackswill have wrappers &quot;if (tdx) tdx_op() else vmx_op()&quot; to pick VMX orTDX at run time.To split the runtime switch, the VMX implementation, and the TDXimplementation, add main.c, and move out the vmx_x86_ops hooks inpreparation for adding TDX.  Use &apos;vt&apos; for the naming scheme as a nod toVT-x and as a concatenation of VmxTdx.The eventually converted code will look like this:vmx.c:  vmx_op() { ... }  VMX initializationtdx.c:  tdx_op() { ... }  TDX initializationx86_ops.h:  vmx_op();  tdx_op();main.c:  static vt_op() { if (tdx) tdx_op() else vmx_op() }  static struct kvm_x86_ops vt_x86_ops = {        .op = vt_op,  initialization functions call both VMX and TDX initializationOpportunistically, fix the name inconsistency from vmx_create_vcpu() andvmx_free_vcpu() to vmx_vcpu_create() and vmx_vcpu_free().Co-developed-by: Xiaoyao Li &lt;xiaoyao.li@intel.com&gt;Signed-off-by: Xiaoyao Li &lt;xiaoyao.li@intel.com&gt;Signed-off-by: Sean Christopherson &lt;seanjc@google.com&gt;Signed-off-by: Isaku Yamahata &lt;isaku.yamahata@intel.com&gt;Reviewed-by: Binbin Wu &lt;binbin.wu@linux.intel.com&gt;Reviewed-by: Xiaoyao Li &lt;xiaoyao.li@intel.com&gt;Reviewed-by: Yuan Yao &lt;yuan.yao@intel.com&gt;Message-Id: &lt;e603c317587f933a9d1bee8728c84e4935849c16.1705965634.git.isaku.yamahata@intel.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Mon, 18 Mar 2024 15:39:16 +0000</pubDate>
        <dc:creator>Paolo Bonzini &lt;pbonzini@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>0d7bf5e5 - KVM: SVM: Compile sev.c if and only if CONFIG_KVM_AMD_SEV=y</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#0d7bf5e5</link>
        <description>KVM: SVM: Compile sev.c if and only if CONFIG_KVM_AMD_SEV=yStop compiling sev.c when CONFIG_KVM_AMD_SEV=n, as the number of #ifdefsin sev.c is getting ridiculous, and having #ifdefs inside of SEV helpersis quite confusing.To minimize #ifdefs in code flows, #ifdef away only the kvm_x86_ops hooksand the #VMGEXIT handler. Stubs are also restricted to functions thatcheck sev_enabled and to the destruction functions sev_free_cpu() andsev_vm_destroy(), where the style of their callers is to leave checksto the callers.  Most call sites instead rely on dead code eliminationto take care of functions that are guarded with sev_guest() orsev_es_guest().Signed-off-by: Sean Christopherson &lt;seanjc@google.com&gt;Co-developed-by: Sean Christopherson &lt;seanjc@google.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;Message-ID: &lt;20240404121327.3107131-3-pbonzini@redhat.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Thu, 04 Apr 2024 12:13:12 +0000</pubDate>
        <dc:creator>Paolo Bonzini &lt;pbonzini@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>27ca8670 - KVM: x86: Stop compiling vmenter.S with OBJECT_FILES_NON_STANDARD</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#27ca8670</link>
        <description>KVM: x86: Stop compiling vmenter.S with OBJECT_FILES_NON_STANDARDStop compiling vmenter.S with OBJECT_FILES_NON_STANDARD to skip objtool&apos;sstack validation now that __svm_vcpu_run() and __svm_sev_es_vcpu_run()create stack frames (though the former&apos;s effectiveness is dubious).Note, due to a quirk in how OBJECT_FILES_NON_STANDARD was handled by thebuild system prior to commit bf48d9b756b9 (&quot;kbuild: change tool coveragevariables to take the path relative to $(obj)&quot;), vmx/vmenter.S got lumpedin with svm/vmenter.S.  __vmx_vcpu_run() already plays nice with framepointers, i.e. it was collateral damage when commit 7f4b5cde2409 (&quot;kvm:Disable objtool frame pointer checking for vmenter.S&quot;) added theOBJECT_FILES_NON_STANDARD hack-a-fix.Link: https://lore.kernel.org/all/20240217055504.2059803-1-masahiroy@kernel.orgReviewed-by: Tom Lendacky &lt;thomas.lendacky@amd.com&gt;Link: https://lore.kernel.org/r/20240223204233.3337324-9-seanjc@google.comSigned-off-by: Sean Christopherson &lt;seanjc@google.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Fri, 23 Feb 2024 20:42:33 +0000</pubDate>
        <dc:creator>Sean Christopherson &lt;seanjc@google.com&gt;</dc:creator>
    </item>
<item>
        <title>bf48d9b7 - kbuild: change tool coverage variables to take the path relative to $(obj)</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#bf48d9b7</link>
        <description>kbuild: change tool coverage variables to take the path relative to $(obj)Commit 54b8ae66ae1a (&quot;kbuild: change *FLAGS_&lt;basetarget&gt;.o to take thepath relative to $(obj)&quot;) changed the syntax of per-file compiler flags.The situation is the same for the following variables:  OBJECT_FILES_NON_STANDARD_&lt;basetarget&gt;.o  GCOV_PROFILE_&lt;basetarget&gt;.o  KASAN_SANITIZE_&lt;basetarget&gt;.o  KMSAN_SANITIZE_&lt;basetarget&gt;.o  KMSAN_ENABLE_CHECKS_&lt;basetarget&gt;.o  UBSAN_SANITIZE_&lt;basetarget&gt;.o  KCOV_INSTRUMENT_&lt;basetarget&gt;.o  KCSAN_SANITIZE_&lt;basetarget&gt;.o  KCSAN_INSTRUMENT_BARRIERS_&lt;basetarget&gt;.oThe &lt;basetarget&gt; is the filename of the target with its directory andsuffix stripped.This syntax comes into a trouble when two files with the same basenameappear in one Makefile, for example:  obj-y += dir1/foo.o  obj-y += dir2/foo.o  OBJECT_FILES_NON_STANDARD_foo.o := yOBJECT_FILES_NON_STANDARD_foo.o is applied to both dir1/foo.o anddir2/foo.o. This syntax is not flexbile enough to handle cases whereone of them is a standard object, but the other is not.It is more sensible to use the relative path to the Makefile, like this:  obj-y += dir1/foo.o  OBJECT_FILES_NON_STANDARD_dir1/foo.o := y  obj-y += dir2/foo.o  OBJECT_FILES_NON_STANDARD_dir2/foo.o := yTo maintain the current behavior, I made adjustments to the following twoMakefiles: - arch/x86/entry/vdso/Makefile, which compiles vclock_gettime.o, vgetcpu.o,   and their vdso32 variants. - arch/x86/kvm/Makefile, which compiles vmx/vmenter.o and svm/vmenter.oSigned-off-by: Masahiro Yamada &lt;masahiroy@kernel.org&gt;Reviewed-by: Nicolas Schier &lt;nicolas@fjasle.eu&gt;Acked-by: Sean Christopherson &lt;seanjc@google.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Sat, 17 Feb 2024 05:55:03 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;masahiroy@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>b4f69df0 - KVM: x86: Make Hyper-V emulation optional</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#b4f69df0</link>
        <description>KVM: x86: Make Hyper-V emulation optionalHyper-V emulation in KVM is a fairly big chunk and in some cases it may bedesirable to not compile it in to reduce module sizes as well as the attacksurface. Introduce CONFIG_KVM_HYPERV option to make it possible.Note, there&apos;s room for further nVMX/nSVM code optimizations when!CONFIG_KVM_HYPERV, this will be done in follow-up patches.Reorganize Makefile a bit so all CONFIG_HYPERV and CONFIG_KVM_HYPERV filesare grouped together.Signed-off-by: Vitaly Kuznetsov &lt;vkuznets@redhat.com&gt;Reviewed-by: Maxim Levitsky &lt;mlevitsk@redhat.com&gt;Tested-by: Jeremi Piotrowski &lt;jpiotrowski@linux.microsoft.com&gt;Link: https://lore.kernel.org/r/20231205103630.1391318-13-vkuznets@redhat.comSigned-off-by: Sean Christopherson &lt;seanjc@google.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Tue, 05 Dec 2023 10:36:26 +0000</pubDate>
        <dc:creator>Vitaly Kuznetsov &lt;vkuznets@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>e7ad84db - KVM: VMX: Split off hyperv_evmcs.{ch}</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#e7ad84db</link>
        <description>KVM: VMX: Split off hyperv_evmcs.{ch}Some Enlightened VMCS related code is needed both by Hyper-V on KVM andKVM on Hyper-V. As a preparation to making Hyper-V emulation optional,create dedicated &apos;hyperv_evmcs.{ch}&apos; files which are used by both.No functional change intended.Reviewed-by: Maxim Levitsky &lt;mlevitsk@redhat.com&gt;Tested-by: Jeremi Piotrowski &lt;jpiotrowski@linux.microsoft.com&gt;Signed-off-by: Vitaly Kuznetsov &lt;vkuznets@redhat.com&gt;Link: https://lore.kernel.org/r/20231205103630.1391318-7-vkuznets@redhat.comSigned-off-by: Sean Christopherson &lt;seanjc@google.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Tue, 05 Dec 2023 10:36:20 +0000</pubDate>
        <dc:creator>Vitaly Kuznetsov &lt;vkuznets@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>50a82b0e - KVM: VMX: Split off vmx_onhyperv.{ch} from hyperv.{ch}</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#50a82b0e</link>
        <description>KVM: VMX: Split off vmx_onhyperv.{ch} from hyperv.{ch}hyperv.{ch} is currently a mix of stuff which is needed by both Hyper-V onKVM and KVM on Hyper-V. As a preparation to making Hyper-V emulationoptional, put KVM-on-Hyper-V specific code into dedicated files.No functional change intended.Reviewed-by: Maxim Levitsky &lt;mlevitsk@redhat.com&gt;Tested-by: Jeremi Piotrowski &lt;jpiotrowski@linux.microsoft.com&gt;Signed-off-by: Vitaly Kuznetsov &lt;vkuznets@redhat.com&gt;Link: https://lore.kernel.org/r/20231205103630.1391318-4-vkuznets@redhat.comSigned-off-by: Sean Christopherson &lt;seanjc@google.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Tue, 05 Dec 2023 10:36:17 +0000</pubDate>
        <dc:creator>Vitaly Kuznetsov &lt;vkuznets@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>b0c9c25e - KVM: x86: Introduce .hv_inject_synthetic_vmexit_post_tlb_flush() nested hook</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#b0c9c25e</link>
        <description>KVM: x86: Introduce .hv_inject_synthetic_vmexit_post_tlb_flush() nested hookHyper-V supports injecting synthetic L2-&gt;L1 exit after performingL2 TLB flush operation but the procedure is vendor specific. Introduce.hv_inject_synthetic_vmexit_post_tlb_flush nested hook for it.Reviewed-by: Maxim Levitsky &lt;mlevitsk@redhat.com&gt;Reviewed-by: Sean Christopherson &lt;seanjc@google.com&gt;Signed-off-by: Vitaly Kuznetsov &lt;vkuznets@redhat.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;Message-Id: &lt;20221101145426.251680-22-vkuznets@redhat.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Tue, 01 Nov 2022 14:53:59 +0000</pubDate>
        <dc:creator>Vitaly Kuznetsov &lt;vkuznets@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>a789aeba - KVM: VMX: Rename &quot;vmx/evmcs.{ch}&quot; to &quot;vmx/hyperv.{ch}&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#a789aeba</link>
        <description>KVM: VMX: Rename &quot;vmx/evmcs.{ch}&quot; to &quot;vmx/hyperv.{ch}&quot;To conform with SVM, rename VMX specific Hyper-V files from &quot;evmcs.{ch}&quot;to &quot;hyperv.{ch}&quot;. While Enlightened VMCS is a lion&apos;s share of thesefiles, some stuff (e.g. enlightened MSR bitmap, the upcoming Hyper-VL2 TLB flush, ...) goes beyond that.Reviewed-by: Sean Christopherson &lt;seanjc@google.com&gt;Signed-off-by: Vitaly Kuznetsov &lt;vkuznets@redhat.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;Message-Id: &lt;20221101145426.251680-7-vkuznets@redhat.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Tue, 01 Nov 2022 14:53:44 +0000</pubDate>
        <dc:creator>Vitaly Kuznetsov &lt;vkuznets@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>4b8e1b32 - KVM: allow compiling out SMM support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#4b8e1b32</link>
        <description>KVM: allow compiling out SMM supportSome users of KVM implement the UEFI variable store through a paravirtual devicethat does not require the &quot;SMM lockbox&quot; component of edk2; allow them tocompile out system management mode, which is not a full implementationespecially in how it interacts with nested virtualization.Suggested-by: Sean Christopherson &lt;seanjc@google.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;Reviewed-by: Maxim Levitsky &lt;mlevitsk@redhat.com&gt;Message-Id: &lt;20220929172016.319443-6-pbonzini@redhat.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Thu, 29 Sep 2022 17:20:13 +0000</pubDate>
        <dc:creator>Paolo Bonzini &lt;pbonzini@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>b0b42197 - KVM: x86: start moving SMM-related functions to new files</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#b0b42197</link>
        <description>KVM: x86: start moving SMM-related functions to new filesCreate a new header and source with code related to system managementmode emulation.  Entry and exit will move there too; for now,opportunistically rename put_smstate to PUT_SMSTATE while movingit to smm.h, and adjust the SMM state saving code.Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;Reviewed-by: Maxim Levitsky &lt;mlevitsk@redhat.com&gt;Message-Id: &lt;20220929172016.319443-2-pbonzini@redhat.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Thu, 29 Sep 2022 17:20:09 +0000</pubDate>
        <dc:creator>Paolo Bonzini &lt;pbonzini@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>16fdc1de - KVM: SVM: replace regs argument of __svm_vcpu_run() with vcpu_svm</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#16fdc1de</link>
        <description>KVM: SVM: replace regs argument of __svm_vcpu_run() with vcpu_svmSince registers are reachable through vcpu_svm, and we willneed to access more fields of that struct, pass it insteadof the regs[] array.No functional change intended.Cc: stable@vger.kernel.orgFixes: a149180fbcf3 (&quot;x86: Add magic AMD return-thunk&quot;)Reviewed-by: Sean Christopherson &lt;seanjc@google.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Fri, 30 Sep 2022 18:14:44 +0000</pubDate>
        <dc:creator>Paolo Bonzini &lt;pbonzini@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>debc5a1e - KVM: x86: use a separate asm-offsets.c file</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#debc5a1e</link>
        <description>KVM: x86: use a separate asm-offsets.c fileThis already removes an ugly #include &quot;&quot; from asm-offsets.c, butespecially it avoids a future error when trying to define asm-offsetsfor KVM&apos;s svm/svm.h header.This would not work for kernel/asm-offsets.c, because svm/svm.hincludes kvm_cache_regs.h which is not in the include path whencompiling asm-offsets.c.  The problem is not there if the .c file isin arch/x86/kvm.Suggested-by: Sean Christopherson &lt;seanjc@google.com&gt;Cc: stable@vger.kernel.orgFixes: a149180fbcf3 (&quot;x86: Add magic AMD return-thunk&quot;)Reviewed-by: Sean Christopherson &lt;seanjc@google.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Tue, 08 Nov 2022 08:44:53 +0000</pubDate>
        <dc:creator>Paolo Bonzini &lt;pbonzini@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>6f2cdbdb - KVM: Add Makefile.kvm for common files, use it for x86</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#6f2cdbdb</link>
        <description>KVM: Add Makefile.kvm for common files, use it for x86Splitting kvm_main.c out into smaller and better-organized files isslightly non-trivial when it involves editing a bunch of per-archKVM makefiles. Provide virt/kvm/Makefile.kvm for them to include.Signed-off-by: David Woodhouse &lt;dwmw@amazon.co.uk&gt;Acked-by: Marc Zyngier &lt;maz@kernel.org&gt;Message-Id: &lt;20211121125451.9489-3-dwmw2@infradead.org&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Sun, 21 Nov 2021 12:54:41 +0000</pubDate>
        <dc:creator>David Woodhouse &lt;dwmw@amazon.co.uk&gt;</dc:creator>
    </item>
<item>
        <title>cb082bfa - KVM: stats: Add fd-based API to read binary stats data</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#cb082bfa</link>
        <description>KVM: stats: Add fd-based API to read binary stats dataThis commit defines the API for userspace and prepare the commonfunctionalities to support per VM/VCPU binary stats data readings.The KVM stats now is only accessible by debugfs, which has someshortcomings this change series are supposed to fix:1. The current debugfs stats solution in KVM could be disabled   when kernel Lockdown mode is enabled, which is a potential   rick for production.2. The current debugfs stats solution in KVM is organized as &quot;one   stats per file&quot;, it is good for debugging, but not efficient   for production.3. The stats read/clear in current debugfs solution in KVM are   protected by the global kvm_lock.Besides that, there are some other benefits with this change:1. All KVM VM/VCPU stats can be read out in a bulk by one copy   to userspace.2. A schema is used to describe KVM statistics. From userspace&apos;s   perspective, the KVM statistics are self-describing.3. With the fd-based solution, a separate telemetry would be able   to read KVM stats in a less privileged environment.4. After the initial setup by reading in stats descriptors, a   telemetry only needs to read the stats data itself, no more   parsing or setup is needed.Reviewed-by: David Matlack &lt;dmatlack@google.com&gt;Reviewed-by: Ricardo Koller &lt;ricarkol@google.com&gt;Reviewed-by: Krish Sadhukhan &lt;krish.sadhukhan@oracle.com&gt;Reviewed-by: Fuad Tabba &lt;tabba@google.com&gt;Tested-by: Fuad Tabba &lt;tabba@google.com&gt; #arm64Signed-off-by: Jing Zhang &lt;jingzhangos@google.com&gt;Message-Id: &lt;20210618222709.1858088-3-jingzhangos@google.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Fri, 18 Jun 2021 22:27:04 +0000</pubDate>
        <dc:creator>Jing Zhang &lt;jingzhangos@google.com&gt;</dc:creator>
    </item>
<item>
        <title>1183646a - KVM: SVM: hyper-v: Direct Virtual Flush support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#1183646a</link>
        <description>KVM: SVM: hyper-v: Direct Virtual Flush supportFrom Hyper-V TLFS: &quot;The hypervisor exposes hypercalls (HvFlushVirtualAddressSpace,  HvFlushVirtualAddressSpaceEx, HvFlushVirtualAddressList, and  HvFlushVirtualAddressListEx) that allow operating systems to more  efficiently manage the virtual TLB. The L1 hypervisor can choose to  allow its guest to use those hypercalls and delegate the responsibility  to handle them to the L0 hypervisor. This requires the use of a  partition assist page.&quot;Add the Direct Virtual Flush support for SVM.Related VMX changes:commit 6f6a657c9998 (&quot;KVM/Hyper-V/VMX: Add direct tlb flush support&quot;)Signed-off-by: Vineeth Pillai &lt;viremana@linux.microsoft.com&gt;Message-Id: &lt;fc8d24d8eb7017266bb961e39a171b0caf298d7f.1622730232.git.viremana@linux.microsoft.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Thu, 03 Jun 2021 15:14:40 +0000</pubDate>
        <dc:creator>Vineeth Pillai &lt;viremana@linux.microsoft.com&gt;</dc:creator>
    </item>
<item>
        <title>3c86c0d3 - KVM: x86: hyper-v: Move the remote TLB flush logic out of vmx</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#3c86c0d3</link>
        <description>KVM: x86: hyper-v: Move the remote TLB flush logic out of vmxCurrently the remote TLB flush logic is specific to VMX.Move it to a common place so that SVM can use it as well.Signed-off-by: Vineeth Pillai &lt;viremana@linux.microsoft.com&gt;Message-Id: &lt;4f4e4ca19778437dae502f44363a38e99e3ef5d1.1622730232.git.viremana@linux.microsoft.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Thu, 03 Jun 2021 15:14:36 +0000</pubDate>
        <dc:creator>Vineeth Pillai &lt;viremana@linux.microsoft.com&gt;</dc:creator>
    </item>
<item>
        <title>9798adbc - KVM: VMX: Frame in ENCLS handler for SGX virtualization</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#9798adbc</link>
        <description>KVM: VMX: Frame in ENCLS handler for SGX virtualizationIntroduce sgx.c and sgx.h, along with the framework for handling ENCLSVM-Exits.  Add a bool, enable_sgx, that will eventually be wired up to amodule param to control whether or not SGX virtualization is enabled atruntime.Signed-off-by: Sean Christopherson &lt;sean.j.christopherson@intel.com&gt;Signed-off-by: Kai Huang &lt;kai.huang@intel.com&gt;Message-Id: &lt;1c782269608b2f5e1034be450f375a8432fb705d.1618196135.git.kai.huang@intel.com&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Mon, 12 Apr 2021 04:21:38 +0000</pubDate>
        <dc:creator>Sean Christopherson &lt;sean.j.christopherson@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>6fb3084a - KVM: make: Fix out-of-source module builds</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/x86/kvm/Makefile#6fb3084a</link>
        <description>KVM: make: Fix out-of-source module buildsBuilding kvm module out-of-source with,    make -C $SRC O=$BIN M=arch/x86/kvmfails to find &quot;irq.h&quot; as the include dir passed to cflags-y does notprefix the source dir. Fix this by prefixing $(srctree) to the includedir path.Signed-off-by: Siddharth Chandrasekaran &lt;sidcha@amazon.de&gt;Message-Id: &lt;20210324124347.18336-1-sidcha@amazon.de&gt;Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;

            List of files:
            /linux-6.15/arch/x86/kvm/Makefile</description>
        <pubDate>Wed, 24 Mar 2021 12:43:47 +0000</pubDate>
        <dc:creator>Siddharth Chandrasekaran &lt;sidcha@amazon.de&gt;</dc:creator>
    </item>
</channel>
</rss>
