From: Zhao Liu <zhao1.liu@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
"Michael S . Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Cc: Xiaoyao Li <xiaoyao.li@intel.com>,
Pankaj Gupta <pankaj.gupta@amd.com>,
Zide Chen <zide.chen@intel.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
Zhao Liu <zhao1.liu@intel.com>
Subject: [PATCH v2 0/6] target/i386: Misc cleanup on KVM PV defs and outdated comments
Date: Mon, 6 May 2024 16:51:47 +0800 [thread overview]
Message-ID: <20240506085153.2834841-1-zhao1.liu@intel.com> (raw)
Hi,
This is my v2 cleanup series. Compared with v1 [1], only tags (R/b, S/b)
updates, and a typo fix, no code change.
This series picks cleanup from my previous kvmclock [2] (as other
renaming attempts were temporarily put on hold).
In addition, this series also include the cleanup on a historically
workaround and recent comment of coco interface [3].
Avoiding the fragmentation of these misc cleanups, I consolidated them
all in one series and was able to tackle them in one go!
[1]: https://lore.kernel.org/qemu-devel/20240426100716.2111688-1-zhao1.liu@intel.com/
[2]: https://lore.kernel.org/qemu-devel/20240329101954.3954987-1-zhao1.liu@linux.intel.com/
[3]: https://lore.kernel.org/qemu-devel/2815f0f1-9e20-4985-849c-d74c6cdc94ae@intel.com/
Thanks and Best Regards,
Zhao
---
Zhao Liu (6):
target/i386/kvm: Add feature bit definitions for KVM CPUID
target/i386/kvm: Remove local MSR_KVM_WALL_CLOCK and
MSR_KVM_SYSTEM_TIME definitions
target/i386/kvm: Only save/load kvmclock MSRs when kvmclock enabled
target/i386/kvm: Save/load MSRs of kvmclock2
(KVM_FEATURE_CLOCKSOURCE2)
target/i386/kvm: Drop workaround for KVM_X86_DISABLE_EXITS_HTL typo
target/i386/confidential-guest: Fix comment of
x86_confidential_guest_kvm_type()
hw/i386/kvm/clock.c | 5 +--
target/i386/confidential-guest.h | 2 +-
target/i386/cpu.h | 25 +++++++++++++
target/i386/kvm/kvm.c | 63 +++++++++++++++++++-------------
4 files changed, 66 insertions(+), 29 deletions(-)
--
2.34.1
next reply other threads:[~2024-05-06 8:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 8:51 Zhao Liu [this message]
2024-05-06 8:51 ` [PATCH v2 1/6] target/i386/kvm: Add feature bit definitions for KVM CPUID Zhao Liu
2024-05-06 8:51 ` [PATCH v2 2/6] target/i386/kvm: Remove local MSR_KVM_WALL_CLOCK and MSR_KVM_SYSTEM_TIME definitions Zhao Liu
2024-05-06 8:51 ` [PATCH v2 3/6] target/i386/kvm: Only save/load kvmclock MSRs when kvmclock enabled Zhao Liu
2024-05-06 8:51 ` [PATCH v2 4/6] target/i386/kvm: Save/load MSRs of kvmclock2 (KVM_FEATURE_CLOCKSOURCE2) Zhao Liu
2024-05-06 8:51 ` [PATCH v2 5/6] target/i386/kvm: Drop workaround for KVM_X86_DISABLE_EXITS_HTL typo Zhao Liu
2024-05-06 8:51 ` [PATCH v2 6/6] target/i386/confidential-guest: Fix comment of x86_confidential_guest_kvm_type() Zhao Liu
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=20240506085153.2834841-1-zhao1.liu@intel.com \
--to=zhao1.liu@intel.com \
--cc=eduardo@habkost.net \
--cc=kvm@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pankaj.gupta@amd.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=xiaoyao.li@intel.com \
--cc=zide.chen@intel.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 read-only IMAP folder(s) and NNTP newsgroup(s).