Re: [PATCH v2 41/50] KVM: Rename and move CPUHP_AP_KVM_STARTING to ONLINE section

[PATCH v2 00/50] KVM: Rework kvm_init() and hardware enabling · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 01/50] KVM: Register /dev/kvm as the _very_ last thing during initialization · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 02/50] KVM: Initialize IRQ FD after arch hardware setup · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 03/50] KVM: Allocate cpus_hardware_enabled after arch hardware setup · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 04/50] KVM: Teardown VFIO ops earlier in kvm_exit() · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 05/50] KVM: s390: Unwind kvm_arch_init() piece-by-piece() if a step fails · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 06/50] KVM: s390: Move hardware setup/unsetup to init/exit · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 07/50] KVM: x86: Do timer initialization after XCR0 configuration · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 08/50] KVM: x86: Move hardware setup/unsetup to init/exit · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 09/50] KVM: Drop arch hardware (un)setup hooks · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 10/50] KVM: VMX: Reset eVMCS controls in VP assist page during hardware disabling · Sean Christopherson <seanjc@google.com> · 2022-11-30
Re: [PATCH v2 10/50] KVM: VMX: Reset eVMCS controls in VP assist page during hardware disabling · Vitaly Kuznetsov <vkuznets@redhat.com> · 2022-12-01
[PATCH v2 11/50] KVM: VMX: Don't bother disabling eVMCS static key on module exit · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 15/50] KVM: x86: Serialize vendor module initialization (hardware setup) · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 17/50] KVM: arm64: Free hypervisor allocations if vector slot init fails · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 12/50] KVM: VMX: Move Hyper-V eVMCS initialization to helper · Sean Christopherson <seanjc@google.com> · 2022-11-30
Re: [PATCH v2 12/50] KVM: VMX: Move Hyper-V eVMCS initialization to helper · Vitaly Kuznetsov <vkuznets@redhat.com> · 2022-12-01
[PATCH v2 18/50] KVM: arm64: Unregister perf callbacks if hypervisor finalization fails · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 13/50] KVM: x86: Move guts of kvm_arch_init() to standalone helper · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 14/50] KVM: VMX: Do _all_ initialization before exposing /dev/kvm to userspace · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 16/50] KVM: arm64: Simplify the CPUHP logic · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 27/50] KVM: s390: Do s390 specific init without bouncing through kvm_init() · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 19/50] KVM: arm64: Do arm/arch initialization without bouncing through kvm_init() · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 20/50] KVM: arm64: Mark kvm_arm_init() and its unique descendants as __init · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 21/50] KVM: MIPS: Hardcode callbacks to hardware virtualization extensions · Sean Christopherson <seanjc@google.com> · 2022-11-30
Re: [PATCH v2 21/50] KVM: MIPS: Hardcode callbacks to hardware virtualization extensions · Philippe Mathieu-Daudé <hidden> · 2022-12-01
Re: [PATCH v2 21/50] KVM: MIPS: Hardcode callbacks to hardware virtualization extensions · Sean Christopherson <seanjc@google.com> · 2022-12-01
[PATCH v2 22/50] KVM: MIPS: Setup VZ emulation? directly from kvm_mips_init() · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 23/50] KVM: MIPS: Register die notifier prior to kvm_init() · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 24/50] KVM: RISC-V: Do arch init directly in riscv_kvm_init() · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 37/50] KVM: VMX: Shuffle support checks and hardware enabling code around · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 25/50] KVM: RISC-V: Tag init functions and data with __init, __ro_after_init · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 26/50] KVM: PPC: Move processor compatibility check to module init · Sean Christopherson <seanjc@google.com> · 2022-11-30
Re: [PATCH v2 26/50] KVM: PPC: Move processor compatibility check to module init · Michael Ellerman <mpe@ellerman.id.au> · 2022-12-01
Re: [PATCH v2 26/50] KVM: PPC: Move processor compatibility check to module init · Sean Christopherson <seanjc@google.com> · 2022-12-01
[PATCH v2 28/50] KVM: s390: Mark __kvm_s390_init() and its descendants as __init · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 29/50] KVM: Drop kvm_arch_{init,exit}() hooks · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 41/50] KVM: Rename and move CPUHP_AP_KVM_STARTING to ONLINE section · Sean Christopherson <seanjc@google.com> · 2022-11-30
Re: [PATCH v2 41/50] KVM: Rename and move CPUHP_AP_KVM_STARTING to ONLINE section · Huang, Kai <hidden> · 2022-12-02
Re: [PATCH v2 41/50] KVM: Rename and move CPUHP_AP_KVM_STARTING to ONLINE section · Sean Christopherson <seanjc@google.com> · 2022-12-02
[PATCH v2 40/50] KVM: x86: Do compatibility checks when onlining CPU · Sean Christopherson <seanjc@google.com> · 2022-11-30
Re: [PATCH v2 40/50] KVM: x86: Do compatibility checks when onlining CPU · Huang, Kai <hidden> · 2022-12-02
Re: [PATCH v2 40/50] KVM: x86: Do compatibility checks when onlining CPU · Huang, Kai <hidden> · 2022-12-02
Re: [PATCH v2 40/50] KVM: x86: Do compatibility checks when onlining CPU · Sean Christopherson <seanjc@google.com> · 2022-12-02
[PATCH v2 30/50] KVM: VMX: Make VMCS configuration/capabilities structs read-only after init · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 31/50] KVM: x86: Do CPU compatibility checks in x86 code · Sean Christopherson <seanjc@google.com> · 2022-11-30
Re: [PATCH v2 31/50] KVM: x86: Do CPU compatibility checks in x86 code · Huang, Kai <hidden> · 2022-12-02
Re: [PATCH v2 31/50] KVM: x86: Do CPU compatibility checks in x86 code · Isaku Yamahata <hidden> · 2022-12-05
Re: [PATCH v2 31/50] KVM: x86: Do CPU compatibility checks in x86 code · Sean Christopherson <seanjc@google.com> · 2022-12-05
[PATCH v2 32/50] KVM: Drop kvm_arch_check_processor_compat() hook · Sean Christopherson <seanjc@google.com> · 2022-11-30
Re: [PATCH v2 32/50] KVM: Drop kvm_arch_check_processor_compat() hook · Huang, Kai <hidden> · 2022-12-02
[PATCH v2 33/50] KVM: x86: Use KBUILD_MODNAME to specify vendor module name · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 35/50] KVM: VMX: Use current CPU's info to perform "disabled by BIOS?" checks · Sean Christopherson <seanjc@google.com> · 2022-11-30
Re: [PATCH v2 35/50] KVM: VMX: Use current CPU's info to perform "disabled by BIOS?" checks · Huang, Kai <hidden> · 2022-12-02
[PATCH v2 34/50] KVM: x86: Unify pr_fmt to use module name for all KVM modules · Sean Christopherson <seanjc@google.com> · 2022-11-30
Re: [PATCH v2 34/50] KVM: x86: Unify pr_fmt to use module name for all KVM modules · Paul Durrant <hidden> · 2022-12-01
[PATCH v2 36/50] KVM: x86: Do VMX/SVM support checks directly in vendor code · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 38/50] KVM: SVM: Check for SVM support in CPU compatibility checks · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 39/50] KVM: x86: Move CPU compat checks hook to kvm_x86_ops (from kvm_x86_init_ops) · Sean Christopherson <seanjc@google.com> · 2022-11-30
Re: [PATCH v2 39/50] KVM: x86: Move CPU compat checks hook to kvm_x86_ops (from kvm_x86_init_ops) · Huang, Kai <hidden> · 2022-12-02
Re: [PATCH v2 39/50] KVM: x86: Move CPU compat checks hook to kvm_x86_ops (from kvm_x86_init_ops) · Isaku Yamahata <hidden> · 2022-12-05
[PATCH v2 42/50] KVM: Disable CPU hotplug during hardware enabling/disabling · Sean Christopherson <seanjc@google.com> · 2022-11-30
Re: [PATCH v2 42/50] KVM: Disable CPU hotplug during hardware enabling/disabling · Huang, Kai <hidden> · 2022-12-02
Re: [PATCH v2 42/50] KVM: Disable CPU hotplug during hardware enabling/disabling · Sean Christopherson <seanjc@google.com> · 2022-12-02
[PATCH v2 43/50] KVM: Ensure CPU is stable during low level hardware enable/disable · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 44/50] KVM: Drop kvm_count_lock and instead protect kvm_usage_count with kvm_lock · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 45/50] KVM: Remove on_each_cpu(hardware_disable_nolock) in kvm_exit() · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 46/50] KVM: Use a per-CPU variable to track which CPUs have enabled virtualization · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 47/50] KVM: Make hardware_enable_failed a local variable in the "enable all" path · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 50/50] KVM: Clean up error labels in kvm_init() · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 48/50] KVM: Register syscore (suspend/resume) ops early in kvm_init() · Sean Christopherson <seanjc@google.com> · 2022-11-30
[PATCH v2 49/50] KVM: Opt out of generic hardware enabling on s390 and PPC · Sean Christopherson <seanjc@google.com> · 2022-11-30
Re: [PATCH v2 00/50] KVM: Rework kvm_init() and hardware enabling · Chao Gao <hidden> · 2022-12-02
Re: [PATCH v2 00/50] KVM: Rework kvm_init() and hardware enabling · Paolo Bonzini <pbonzini@redhat.com> · 2022-12-27
Re: [PATCH v2 00/50] KVM: Rework kvm_init() and hardware enabling · Marc Zyngier <maz@kernel.org> · 2022-12-28
Re: [PATCH v2 00/50] KVM: Rework kvm_init() and hardware enabling · Paolo Bonzini <pbonzini@redhat.com> · 2022-12-28
Re: [PATCH v2 00/50] KVM: Rework kvm_init() and hardware enabling · Paolo Bonzini <pbonzini@redhat.com> · 2022-12-29

From: Sean Christopherson <seanjc@google.com>
Date: 2022-12-02 16:08:17
Also in: kvm, kvm-riscv, kvmarm, linux-arm-kernel, linux-mips, linux-riscv, linux-s390, lkml

On Fri, Dec 02, 2022, Huang, Kai wrote:

On Wed, 2022-11-30 at 23:09 +0000, Sean Christopherson wrote:

quoted

From: Chao Gao <redacted>

...

quoted

Suggested-by: Thomas Gleixner <redacted>
Signed-off-by: Chao Gao <redacted>
Signed-off-by: Isaku Yamahata <redacted>

Perhaps I am wrong, but I have memory that if someone has SoB but isn't the
original author should also have a Co-developed-by?

This is the case where a patched is passed along as-is, e.g. same as when
maintainers apply a patch.  Isaku posted Chao's patch, and then I came along and
grabbed the patch that Isaku posted.  I could go back and grab Chao's patch
directly, but Yuan's review was provided for the version Isaku posted, so I
grabbed that version.

quoted

Reviewed-by: Yuan Yao <redacted>
[sean: drop WARN that IRQs are disabled]
Signed-off-by: Sean Christopherson <seanjc@google.com>

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help