From: isaku.yamahata@intel.com
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Marc Zyngier <maz@kernel.org>
Cc: isaku.yamahata@intel.com, isaku.yamahata@gmail.com
Subject: [PATCH 0/4] KVM: simplify hardware initialization
Date: Tue, 1 Nov 2022 23:24:07 -0700 [thread overview]
Message-ID: <cover.1667369456.git.isaku.yamahata@intel.com> (raw)
From: Isaku Yamahata <isaku.yamahata@intel.com>
This patch series include random simplifications of KVM hardware enable/disable.
Although the past attempt [1] was turned out to be a bad idea, it has still
useful patches. This is small subset of [1].
[1] https://lore.kernel.org/kvm/cover.1663869838.git.isaku.yamahata@intel.com/
Isaku Yamahata (3):
KVM: Remove on_each_cpu(hardware_disable_nolock) in kvm_exit()
KVM: Make cpus_hardware_enabled cpumask_t instead of cpumask_var_t
KVM: kvm_main.c: Remove a global variable, hardware_enable_failed
Marc Zyngier (1):
KVM: arm64: Simplify the CPUHP logic
arch/arm64/kvm/arch_timer.c | 27 +++++++------------
arch/arm64/kvm/arm.c | 13 +++++++++
arch/arm64/kvm/vgic/vgic-init.c | 19 ++-----------
include/kvm/arm_arch_timer.h | 4 +++
include/kvm/arm_vgic.h | 4 +++
include/linux/cpuhotplug.h | 3 ---
virt/kvm/kvm_main.c | 48 ++++++++++++++++-----------------
7 files changed, 56 insertions(+), 62 deletions(-)
--
2.25.1
next reply other threads:[~2022-11-02 6:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 6:24 isaku.yamahata [this message]
2022-11-02 6:24 ` [PATCH 1/4] KVM: Remove on_each_cpu(hardware_disable_nolock) in kvm_exit() isaku.yamahata
2022-11-02 6:24 ` [PATCH 2/4] KVM: Make cpus_hardware_enabled cpumask_t instead of cpumask_var_t isaku.yamahata
2022-11-02 6:24 ` [PATCH 3/4] KVM: kvm_main.c: Remove a global variable, hardware_enable_failed isaku.yamahata
2022-11-02 6:24 ` [PATCH 4/4] KVM: arm64: Simplify the CPUHP logic isaku.yamahata
2022-11-02 15:39 ` [PATCH 0/4] KVM: simplify hardware initialization Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1667369456.git.isaku.yamahata@intel.com \
--to=isaku.yamahata@intel.com \
--cc=isaku.yamahata@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox