From: Aaron Lewis <aaronlewis@google.com>
To: kvm@vger.kernel.org
Cc: Jim Mattson <jmattson@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Aaron Lewis <aaronlewis@google.com>
Subject: [PATCH v3 0/5] Add support for capturing the highest observable L2 TSC
Date: Thu, 7 Nov 2019 14:49:36 -0800 [thread overview]
Message-ID: <20191107224941.60336-1-aaronlewis@google.com> (raw)
The L1 hypervisor may include the IA32_TIME_STAMP_COUNTER MSR in the
vmcs12 MSR VM-exit MSR-store area as a way of determining the highest
TSC value that might have been observed by L2 prior to VM-exit. The
current implementation does not capture a very tight bound on this
value. To tighten the bound, add the IA32_TIME_STAMP_COUNTER MSR to the
vmcs02 VM-exit MSR-store area whenever it appears in the vmcs12 VM-exit
MSR-store area. When L0 processes the vmcs12 VM-exit MSR-store area
during the emulation of an L2->L1 VM-exit, special-case the
IA32_TIME_STAMP_COUNTER MSR, using the value stored in the vmcs02
VM-exit MSR-store area to derive the value to be stored in the vmcs12
VM-exit MSR-store area.
v2 -> v3:
- Rename NR_MSR_ENTRIES to NR_LOADSAVE_MSRS
- Pull setup code for preparing the MSR-store area out of the final commit and
put it in it's own commit (4/5).
- Export vmx_find_msr_index() in the final commit instead of in commit 3/5 as
it isn't until the final commit that we actually use it.
v1 -> v2:
- Rename function nested_vmx_get_msr_value() to
nested_vmx_get_vmexit_msr_value().
- Remove unneeded tag 'Change-Id' from commit messages.
Aaron Lewis (5):
kvm: nested: Introduce read_and_check_msr_entry()
kvm: vmx: Rename NR_AUTOLOAD_MSRS to NR_MSR_ENTRIES
kvm: vmx: Rename function find_msr() to vmx_find_msr_index()
KVM: nVMX: Prepare MSR-store area
KVM: nVMX: Add support for capturing highest observable L2 TSC
arch/x86/kvm/vmx/nested.c | 136 ++++++++++++++++++++++++++++++++------
arch/x86/kvm/vmx/vmx.c | 14 ++--
arch/x86/kvm/vmx/vmx.h | 9 ++-
3 files changed, 131 insertions(+), 28 deletions(-)
--
2.24.0.432.g9d3f5f5b63-goog
next reply other threads:[~2019-11-07 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 22:49 Aaron Lewis [this message]
2019-11-07 22:49 ` [PATCH v3 1/5] kvm: nested: Introduce read_and_check_msr_entry() Aaron Lewis
2019-11-07 22:49 ` [PATCH v3 2/5] kvm: vmx: Rename NR_AUTOLOAD_MSRS to NR_LOADSTORE_MSRS Aaron Lewis
2019-11-07 22:49 ` [PATCH v3 3/5] kvm: vmx: Rename function find_msr() to vmx_find_msr_index() Aaron Lewis
2019-11-07 22:49 ` [PATCH v3 4/5] KVM: nVMX: Prepare MSR-store area Aaron Lewis
2019-11-07 23:00 ` Liran Alon
2019-11-08 4:49 ` Aaron Lewis
2019-11-07 22:49 ` [PATCH v3 5/5] KVM: nVMX: Add support for capturing highest observable L2 TSC Aaron Lewis
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=20191107224941.60336-1-aaronlewis@google.com \
--to=aaronlewis@google.com \
--cc=jmattson@google.com \
--cc=kvm@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