>>> On 09.04.18 at 16:55, wrote:
> Am Mon, 09 Apr 2018 08:19:53 -0600
> schrieb "Jan Beulich" :
>
>> Is there any guarantee that old hypervisors will send this field as zero
>> (rather than some random value)? If so, I think this should be said
>> explicitly in the commit message, together with t
Am Mon, 09 Apr 2018 08:19:53 -0600
schrieb "Jan Beulich" :
> Is there any guarantee that old hypervisors will send this field as zero
> (rather than some random value)? If so, I think this should be said
> explicitly in the commit message, together with the fact that you
> re-use padding fields.
>>> On 01.04.18 at 22:29, wrote:
> @@ -34,7 +35,8 @@ int handle_tsc_info(struct xc_sr_context *ctx, struct
> xc_sr_record *rec)
> }
>
> if ( xc_domain_set_tsc_info(xch, ctx->domid, tsc->mode,
> -tsc->nsec, tsc->khz, tsc->incarnation) )
> +
On Sun, Apr 01, 2018 at 10:29:58PM +0200, Olaf Hering wrote:
> Add an option to control when vTSC emulation will be activated for a
> domU with tsc_mode=default. Without such option each TSC access from
> domU will be emulated, which causes a significant perfomance drop for
> workloads that make us
