> From: Zhang, Haozhong
> Sent: Tuesday, February 23, 2016 10:05 AM
>
> Both VMX TSC scaling and SVM TSC ratio use the 64-bit TSC scaling ratio,
> but the number of fractional bits of the ratio is different between VMX
> and SVM. This patch adds the architecture code to collect the number of
> fra
On 02/24/16 07:36, Jan Beulich wrote:
> >>> On 23.02.16 at 03:04, wrote:
> > Both VMX TSC scaling and SVM TSC ratio use the 64-bit TSC scaling ratio,
> > but the number of fractional bits of the ratio is different between VMX
> > and SVM. This patch adds the architecture code to collect the number
On 02/24/2016 08:46 AM, Haozhong Zhang wrote:
Sorry, forgot sending the last reply to Boris.
On 02/24/16 14:00, Haozhong Zhang wrote:
On 02/23/16 08:37, Jan Beulich wrote:
On 23.02.16 at 15:16, wrote:
On 02/23/2016 09:10 AM, Jan Beulich wrote:
On 23.02.16 at 15:00, wrote:
On 02/22/2016 09
>>> On 23.02.16 at 03:04, wrote:
> Both VMX TSC scaling and SVM TSC ratio use the 64-bit TSC scaling ratio,
> but the number of fractional bits of the ratio is different between VMX
> and SVM. This patch adds the architecture code to collect the number of
> fractional bits and other related inform
Sorry, forgot sending the last reply to Boris.
On 02/24/16 14:00, Haozhong Zhang wrote:
> On 02/23/16 08:37, Jan Beulich wrote:
> > >>> On 23.02.16 at 15:16, wrote:
> > > On 02/23/2016 09:10 AM, Jan Beulich wrote:
> > > On 23.02.16 at 15:00, wrote:
> > >>> On 02/22/2016 09:04 PM, Haozhong Zh
On 02/23/16 08:37, Jan Beulich wrote:
> >>> On 23.02.16 at 15:16, wrote:
> > On 02/23/2016 09:10 AM, Jan Beulich wrote:
> > On 23.02.16 at 15:00, wrote:
> >>> On 02/22/2016 09:04 PM, Haozhong Zhang wrote:
> >>>
>
> +if ( cpu_has_tsc_ratio )
> +svm_function_table
>>> On 23.02.16 at 15:16, wrote:
> On 02/23/2016 09:10 AM, Jan Beulich wrote:
> On 23.02.16 at 15:00, wrote:
>>> On 02/22/2016 09:04 PM, Haozhong Zhang wrote:
>>>
+if ( cpu_has_tsc_ratio )
+svm_function_table.tsc_scaling.ratio_frac_bits = 32;
+
>>>
On 02/23/2016 09:10 AM, Jan Beulich wrote:
On 23.02.16 at 15:00, wrote:
On 02/22/2016 09:04 PM, Haozhong Zhang wrote:
+if ( cpu_has_tsc_ratio )
+svm_function_table.tsc_scaling.ratio_frac_bits = 32;
+
+#define hvm_tsc_scaling_supported \
+(!!hvm_funcs.tsc_scaling.rat
>>> On 23.02.16 at 15:00, wrote:
> On 02/22/2016 09:04 PM, Haozhong Zhang wrote:
>
>>
>> +if ( cpu_has_tsc_ratio )
>> +svm_function_table.tsc_scaling.ratio_frac_bits = 32;
>> +
>
>
>>
>> +#define hvm_tsc_scaling_supported \
>> +(!!hvm_funcs.tsc_scaling.ratio_frac_bits)
>>
On 02/22/2016 09:04 PM, Haozhong Zhang wrote:
+if ( cpu_has_tsc_ratio )
+svm_function_table.tsc_scaling.ratio_frac_bits = 32;
+
+#define hvm_tsc_scaling_supported \
+(!!hvm_funcs.tsc_scaling.ratio_frac_bits)
+
What is the difference (in usage) between cpu_has_tsc_rati
Both VMX TSC scaling and SVM TSC ratio use the 64-bit TSC scaling ratio,
but the number of fractional bits of the ratio is different between VMX
and SVM. This patch adds the architecture code to collect the number of
fractional bits and other related information into fields of struct
hvm_function_t
11 matches
Mail list logo
