Am Wed, 05 Jul 2017 02:14:23 -0600
schrieb "Jan Beulich" :
> Oh, even for HVM. Doesn't that go back to the missing vDSO
> support then again, which we had discussed just last week?
Yes. This is part of it. With clocksource=tsc there is a performance boost
because vdso is used. With clocksource=h
>>> On 05.07.17 at 09:25, wrote:
> On Wed, Jul 05, Jan Beulich wrote:
>
>> > clock_getres(CLOCK_MONOTONIC) indicates a resolution of 1ns.
>> But what's the implied meaning of resolution here? See below.
>
> I have no ide what the returned value is supposed to promise.
>
>> Or did you perhaps te
On Wed, Jul 05, Jan Beulich wrote:
> > clock_getres(CLOCK_MONOTONIC) indicates a resolution of 1ns.
> But what's the implied meaning of resolution here? See below.
I have no ide what the returned value is supposed to promise.
> Or did you perhaps test with an older version, where the time
> hand
>>> On 04.07.17 at 18:34, wrote:
> In my testing with sysbench in a HVM domU running a linux-4.4 based
> pvops kernel on a xen-4.7 based dom0 the time does not move forward
> properly:
>
> There (URL below) is basically code like this:
> clock_gettime(CLOCK_MONOTONIC, a)
> do_work
> clock_g
