From: Paolo Bonzini <pbonzini@redhat.com>
To: Yunhong Jiang <yunhong.jiang@linux.intel.com>, kvm@vger.kernel.org
Cc: mtosatti@redhat.com, rkrcmar@redhat.com, kernellwp@gmail.com
Subject: Re: [RFC PATCH V3 3/5] Utilize the vmx preemption timer
Date: Mon, 6 Jun 2016 14:37:47 +0200 [thread overview]
Message-ID: <00a2da92-e504-41a1-a0a0-65836989051f@redhat.com> (raw)
In-Reply-To: <1465000951-13343-4-git-send-email-yunhong.jiang@linux.intel.com>
On 04/06/2016 02:42, Yunhong Jiang wrote:
> +static int vmx_set_hv_timer(struct kvm_vcpu *vcpu, u64 guest_deadline_tsc)
> +{
> + u64 tscl = rdtsc(), delta_tsc;
> +
> + delta_tsc = guest_deadline_tsc - kvm_read_l1_tsc(vcpu, tscl);
> +
> + /* Convert to host delta tsc if tsc scaling is enabled */
> + if (vcpu->arch.tsc_scaling_ratio &&
> + u64_shl_div_u64(delta_tsc,
> + kvm_tsc_scaling_ratio_frac_bits,
> + vcpu->arch.tsc_scaling_ratio,
> + &delta_tsc))
> + return -1;
Please return -EOVERFLOW or -ERANGE. It's just aesthetic, but usually
in Linux functions do not return -1.
Thanks,
Paolo
> + /*
> + * If the delta tsc can't be fit in the 32 bit after the multi shift,
> + * we can't use the preemption timer.
> + * It's possible that it can be fit when vmentry happens late, but
> + * checking on every vmentry is costly, so fail earilier.
> + */
> + if (delta_tsc >> (cpu_preemption_timer_multi + 32))
> + return -1;
> +
> + vcpu->arch.hv_orig_tsc = tscl;
> + vcpu->arch.hv_deadline_tsc = tscl + delta_tsc;
> + vmcs_set_bits(PIN_BASED_VM_EXEC_CONTROL,
> + PIN_BASED_VMX_PREEMPTION_TIMER);
> + return 0;
> +}
next prev parent reply other threads:[~2016-06-06 12:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 0:42 [RFC PATCH V3 0/5] Utilizing VMX preemption for timer virtualization Yunhong Jiang
2016-06-04 0:42 ` [RFC PATCH V3 1/5] Rename the vmx_pre/post_block to pi_pre/post_block Yunhong Jiang
2016-06-04 0:42 ` [RFC PATCH V3 2/5] Add function for left shift and 64 bit division Yunhong Jiang
2016-06-06 12:37 ` Paolo Bonzini
2016-06-04 0:42 ` [RFC PATCH V3 3/5] Utilize the vmx preemption timer Yunhong Jiang
2016-06-06 12:37 ` Paolo Bonzini [this message]
2016-06-04 0:42 ` [RFC PATCH V3 4/5] Separate the start_sw_tscdeadline Yunhong Jiang
2016-06-04 0:42 ` [RFC PATCH V3 5/5] Utilize the vmx preemption timer for tsc deadline timer Yunhong Jiang
2016-06-06 12:36 ` Paolo Bonzini
2016-06-06 12:45 ` [RFC PATCH V3 0/5] Utilizing VMX preemption for timer virtualization Paolo Bonzini
2016-06-06 18:26 ` yunhong jiang
2016-06-07 16:31 ` David Matlack
2016-06-07 19:30 ` David Matlack
2016-06-08 4:18 ` Wanpeng Li
2016-06-13 20:56 ` yunhong jiang
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=00a2da92-e504-41a1-a0a0-65836989051f@redhat.com \
--to=pbonzini@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=yunhong.jiang@linux.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