From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] KVM: x86: Collect host state snapshots into a struct
Date: Tue, 4 Jun 2024 16:29:37 -0700 [thread overview]
Message-ID: <171754330706.2779254.12749909442900108234.b4-ty@google.com> (raw)
In-Reply-To: <20240423221521.2923759-1-seanjc@google.com>
On Tue, 23 Apr 2024 15:15:17 -0700, Sean Christopherson wrote:
> Add a global "kvm_host" structure to hold various host values, e.g. for
> EFER, XCR0, raw MAXPHYADDR etc., instead of having a bunch of one-off
> variables that inevitably need to be exported, or in the case of
> shadow_phys_bits, are buried in a random location and are awkward to use,
> leading to duplicate code.
>
> Sean Christopherson (4):
> KVM: x86: Add a struct to consolidate host values, e.g. EFER, XCR0,
> etc...
> KVM: SVM: Use KVM's snapshot of the host's XCR0 for SEV-ES host state
> KVM: x86/mmu: Snapshot shadow_phys_bits when kvm.ko is loaded
> KVM: x86: Move shadow_phys_bits into "kvm_host", as "maxphyaddr"
>
> [...]
Applied to kvm-x86 misc, thanks!
[1/4] KVM: x86: Add a struct to consolidate host values, e.g. EFER, XCR0, etc...
https://github.com/kvm-x86/linux/commit/7974c0643ee3
[2/4] KVM: SVM: Use KVM's snapshot of the host's XCR0 for SEV-ES host state
https://github.com/kvm-x86/linux/commit/52c47f5897b6
[3/4] KVM: x86/mmu: Snapshot shadow_phys_bits when kvm.ko is loaded
https://github.com/kvm-x86/linux/commit/c043eaaa6be0
[4/4] KVM: x86: Move shadow_phys_bits into "kvm_host", as "maxphyaddr"
https://github.com/kvm-x86/linux/commit/82897db91215
--
https://github.com/kvm-x86/linux/tree/next
prev parent reply other threads:[~2024-06-04 23:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 22:15 Sean Christopherson
2024-04-23 22:15 ` [PATCH 1/4] KVM: x86: Add a struct to consolidate host values, e.g. EFER, XCR0, etc Sean Christopherson
2024-04-25 11:29 ` Wang, Wei W
2024-04-25 14:10 ` Sean Christopherson
2024-04-25 14:37 ` Wang, Wei W
2024-04-25 14:47 ` Sean Christopherson
2024-04-23 22:15 ` [PATCH 2/4] KVM: SVM: Use KVM's snapshot of the host's XCR0 for SEV-ES host state Sean Christopherson
2024-04-23 22:15 ` [PATCH 3/4] KVM: x86/mmu: Snapshot shadow_phys_bits when kvm.ko is loaded Sean Christopherson
2024-04-23 22:15 ` [PATCH 4/4] KVM: x86: Move shadow_phys_bits into "kvm_host", as "maxphyaddr" Sean Christopherson
2024-04-25 11:17 ` [PATCH 0/4] KVM: x86: Collect host state snapshots into a struct Wang, Wei W
2024-04-25 14:24 ` Sean Christopherson
2024-06-04 23:29 ` 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=171754330706.2779254.12749909442900108234.b4-ty@google.com \
--to=seanjc@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®