From: Kai Huang <kai.huang@intel.com>
To: kvm@vger.kernel.org
Cc: pbonzini@redhat.com, bgardon@google.com, seanjc@google.com,
vkuznets@redhat.com, wanpengli@tencent.com, jmattson@google.com,
joro@8bytes.org, Kai Huang <kai.huang@intel.com>
Subject: [PATCH 0/3] TDP MMU: several minor fixes or improvements
Date: Wed, 5 May 2021 21:37:56 +1200 [thread overview]
Message-ID: <cover.1620200410.git.kai.huang@intel.com> (raw)
Pathc 1 and 2 are basically v2 of below patch, after discussion with Ben:
https://lore.kernel.org/kvm/b6d23d9fd8e526e5c7c1a968e2018d13c5433547.camel@intel.com/T/#t
Patch 3 is a new one.
I didn't do lots of tests, especially I didn't do stress test, but only tested
by creating couple of VMs (16 vcpus, 4G memory) and killing them, and everything
seems fine.
Kai Huang (3):
KVM: x86/mmu: Fix return value in tdp_mmu_map_handle_target_level()
KVM: x86/mmu: Fix pf_fixed count in tdp_mmu_map_handle_target_level()
KVM: x86/mmu: Fix TDP MMU page table level
arch/x86/kvm/mmu/tdp_mmu.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
--
2.31.1
next reply other threads:[~2021-05-05 9:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 9:37 Kai Huang [this message]
2021-05-05 9:37 ` [PATCH 1/3] KVM: x86/mmu: Fix return value in tdp_mmu_map_handle_target_level() Kai Huang
2021-05-05 16:00 ` Sean Christopherson
2021-05-05 16:04 ` Ben Gardon
2021-05-06 1:56 ` Kai Huang
2021-05-05 9:37 ` [PATCH 2/3] KVM: x86/mmu: Fix pf_fixed count " Kai Huang
2021-05-05 16:11 ` Ben Gardon
2021-05-06 7:51 ` Kai Huang
2021-05-06 15:29 ` Sean Christopherson
2021-05-06 22:21 ` Kai Huang
2021-05-05 16:29 ` Sean Christopherson
2021-05-05 17:16 ` Sean Christopherson
2021-05-06 1:51 ` Kai Huang
2021-05-05 9:37 ` [PATCH 3/3] KVM: x86/mmu: Fix TDP MMU page table level Kai Huang
2021-05-05 16:28 ` Ben Gardon
2021-05-05 17:01 ` Ben Gardon
2021-05-05 20:19 ` Kai Huang
2021-05-06 8:00 ` Kai Huang
2021-05-06 16:22 ` Ben Gardon
2021-05-06 16:23 ` Ben Gardon
2021-05-06 22:19 ` Kai Huang
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.1620200410.git.kai.huang@intel.com \
--to=kai.huang@intel.com \
--cc=bgardon@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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;
as well as URLs for NNTP newsgroup(s).