search for: clock_monotonic_raw

Greetings, I am writing a code using libvirt API to migrate VM between two physical hosts *(QEMU/KVM) , *say some *n *number of times. *1)* I am using right now* virDomainPtr virDomainMigrate (.......) *and to calculate the total migration time I am using something like this: *clock_gettime(CLOCK_MONOTONIC_RAW,&begin); * *migrate*(domainToMigrate,nodeToMigrate); *clock_gettime(CLOCK_MONOTONIC_RAW,&end);* *Total Migration Time = end.tv_sec-begin.tv_sec* Is this correct way to calculate total migration time. And is there some way to calculate the downtime (not how to set it)? *2) *I am inte...

...a code using libvirt API to migrate VM between two physical > hosts *(QEMU/KVM) , *say some *n *number of times. > > *1)* I am using right now* virDomainPtr virDomainMigrate (.......) *and to > calculate the total migration time I am using something like this: > > *clock_gettime(CLOCK_MONOTONIC_RAW,&begin); * > *migrate*(domainToMigrate,nodeToMigrate); > > *clock_gettime(CLOCK_MONOTONIC_RAW,&end);* > > *Total Migration Time = end.tv_sec-begin.tv_sec* > > Is this correct way to calculate total migration time. And is there some > way to calculate the downtim...

On Tue, Oct 09, 2018 at 01:09:42PM -0700, Andy Lutomirski wrote: > On Tue, Oct 9, 2018 at 8:28 AM Marcelo Tosatti <mtosatti at redhat.com> wrote: > > > > On Mon, Oct 08, 2018 at 10:38:22AM -0700, Andy Lutomirski wrote: > > > On Mon, Oct 8, 2018 at 8:27 AM Marcelo Tosatti <mtosatti at redhat.com> wrote: > > > > I read the comment three more times and

On Tue, Oct 09, 2018 at 01:09:42PM -0700, Andy Lutomirski wrote: > On Tue, Oct 9, 2018 at 8:28 AM Marcelo Tosatti <mtosatti at redhat.com> wrote: > > > > On Mon, Oct 08, 2018 at 10:38:22AM -0700, Andy Lutomirski wrote: > > > On Mon, Oct 8, 2018 at 8:27 AM Marcelo Tosatti <mtosatti at redhat.com> wrote: > > > > I read the comment three more times and

...t; Since pvclock updates which update system_timestamp are expensive (must stop all vcpus), > they should be avoided. > Fair enough. > So only HW TSC counts makes sense. >, and used as offset against vcpu's tsc_timestamp. > Why don't you just expose CLOCK_MONTONIC_RAW or CLOCK_MONOTONIC_RAW plus suspend time, though? Then you would actually be tracking a real kernel timekeeping mode, and you wouldn't need all this complicated offsetting work to avoid accidentally going backwards.

..._old it_value; +}; + +struct timezone { + int tz_minuteswest; + int tz_dsttime; +}; + +#define ITIMER_REAL 0 +#define ITIMER_VIRTUAL 1 +#define TIMER_PROF 2 + +#define CLOCK_REALTIME 0 +#define CLOCK_MONOTONIC 1 +#define CLOCK_PROCESS_CPUTIME_ID 2 +#define CLOCK_THREAD_CPUTIME_ID 3 +#define CLOCK_MONOTONIC_RAW 4 +#define CLOCK_REALTIME_COARSE 5 +#define CLOCK_MONOTONIC_COARSE 6 +#define CLOCK_BOOTTIME 7 +#define CLOCK_REALTIME_ALARM 8 +#define CLOCK_BOOTTIME_ALARM 9 +#define CLOCK_TAI 11 + +#define TIMER_ABSTIME 0x01 /* The 2.6.20 Linux headers always #define FD_ZERO __FD_ZERO, etc, in...

...Include igt.h in gem_blt.c tests/gem_exec_nop: Improved test run time Jani Nikula (3): scripts: remove display_debug.sh as obsolete tools: fix intel_gpu_abrt to use intel_reg tests: fix ddx_intel_after_fbdev to use intel_reg Joonas Lahtinen (1): lib/igt_core: Prefer CLOCK_MONOTONIC_RAW Lu, Han (1): tools/intel_audio_dump: add support for Broxton Maarten Lankhorst (1): tests/kms_setmode: Handle MST correctly. Marius Vlad (1): tests/pm_rpm tests for set_caching and set_tiling ioctl(s) Matt Roper (2): kms_universal_plane: Add gen9-specific test kms_...