From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Jim Mattson <jmattson@google.com>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Peter Shier <pshier@google.com>, Oliver Upton <oupton@google.com>
Subject: Re: [PATCH 1/3] KVM: nVMX: Really make emulated nested preemption timer pinned
Date: Fri, 8 May 2020 15:16:27 -0700 [thread overview]
Message-ID: <20200508221626.GU27052@linux.intel.com> (raw)
In-Reply-To: <20200508203643.85477-2-jmattson@google.com>
LOL, love the shortlog :-)
On Fri, May 08, 2020 at 01:36:41PM -0700, Jim Mattson wrote:
> The PINNED bit is ignored by hrtimer_init. It is only considered when
> starting the timer.
>
> When the hrtimer isn't pinned to the same logical processor as the
> vCPU thread to be interrupted, the emulated VMX-preemption timer
> often fails to adhere to the architectural specification.
>
> Fixes: f15a75eedc18e ("KVM: nVMX: make emulated nested preemption timer pinned")
> Signed-off-by: Jim Mattson <jmattson@google.com>
> Reviewed-by: Peter Shier <pshier@google.com>
> Reviewed-by: Oliver Upton <oupton@google.com>
> ---
> arch/x86/kvm/vmx/nested.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
> index fd78ffbde644..1f7fe6f47cbc 100644
> --- a/arch/x86/kvm/vmx/nested.c
> +++ b/arch/x86/kvm/vmx/nested.c
> @@ -2041,7 +2041,7 @@ static void vmx_start_preemption_timer(struct kvm_vcpu *vcpu)
> preemption_timeout *= 1000000;
> do_div(preemption_timeout, vcpu->arch.virtual_tsc_khz);
> hrtimer_start(&vmx->nested.preemption_timer,
> - ns_to_ktime(preemption_timeout), HRTIMER_MODE_REL);
> + ns_to_ktime(preemption_timeout), HRTIMER_MODE_REL_PINNED);
> }
>
> static u64 nested_vmx_calc_efer(struct vcpu_vmx *vmx, struct vmcs12 *vmcs12)
> --
> 2.26.2.645.ge9eca65c58-goog
>
next prev parent reply other threads:[~2020-05-08 22:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 20:36 [PATCH 0/3] Pin the hrtimer used for VMX-preemption timer emulation Jim Mattson
2020-05-08 20:36 ` [PATCH 1/3] KVM: nVMX: Really make emulated nested preemption timer pinned Jim Mattson
2020-05-08 22:16 ` Sean Christopherson [this message]
2020-05-08 20:36 ` [PATCH 2/3] KVM: nVMX: Change emulated VMX-preemption timer hrtimer to absolute Jim Mattson
2020-05-08 20:36 ` [PATCH 3/3] KVM: nVMX: Migrate the VMX-preemption timer Jim Mattson
2020-05-09 13:17 ` Paolo Bonzini
2020-05-09 13:14 ` [PATCH 0/3] Pin the hrtimer used for VMX-preemption timer emulation Paolo Bonzini
2020-06-19 18:49 ` Jim Mattson
2020-06-19 22:52 ` Paolo Bonzini
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=20200508221626.GU27052@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=oupton@google.com \
--cc=pbonzini@redhat.com \
--cc=pshier@google.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