From: Sean Christopherson <seanjc@google.com>
To: isaku.yamahata@intel.com
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Marc Zyngier <maz@kernel.org>,
isaku.yamahata@gmail.com
Subject: Re: [PATCH 0/4] KVM: simplify hardware initialization
Date: Wed, 2 Nov 2022 15:39:18 +0000 [thread overview]
Message-ID: <Y2KPJjCZn0YKzSJl@google.com> (raw)
In-Reply-To: <cover.1667369456.git.isaku.yamahata@intel.com>
On Tue, Nov 01, 2022, isaku.yamahata@intel.com wrote:
> 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.
I have a larger cleanup that includes all of these patches except "Remove a global
variable, hardware_enable_failed". I was planning on posting the series last weeks,
but I've dealing with a comedy of errors. With luck, I'll get it posted today.
I'll fold in the aforementioned patch as well, there are quite a few conflicts as
my series has a variety of bug fixes before it gets to these cleanups.
prev parent reply other threads:[~2022-11-02 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 6:24 [PATCH 0/4] KVM: simplify hardware initialization isaku.yamahata
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 ` Sean Christopherson [this message]
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=Y2KPJjCZn0YKzSJl@google.com \
--to=seanjc@google.com \
--cc=isaku.yamahata@gmail.com \
--cc=isaku.yamahata@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.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