On Tue, May 14, 2024, 03:57 Zhao Liu wrote:
> Hi Stefan,
>
> > QEMU uses clock_gettime(CLOCK_MONOTONIC) on Linux hosts. The man page
> > says:
> >
> > All CLOCK_MONOTONIC variants guarantee that the time returned by
> > consecutive calls will not go backwards, but successive calls
> >
Hi Stefan,
> QEMU uses clock_gettime(CLOCK_MONOTONIC) on Linux hosts. The man page
> says:
>
> All CLOCK_MONOTONIC variants guarantee that the time returned by
> consecutive calls will not go backwards, but successive calls
> may—depending on the architecture—return identical
> Why are the timestamps non-monotonic?
>
> In a situation like that maybe not only the negative timestamps are
> useless but even some positive timestamps are incorrect. I think it's
> worth understanding the nature of the instability before merging a
> fix.
I agree with Stefan on this. We'll
On Thu, May 09, 2024 at 11:59:10AM +0800, Zhao Liu wrote:
> On Wed, May 08, 2024 at 02:05:04PM -0400, Stefan Hajnoczi wrote:
> > Date: Wed, 8 May 2024 14:05:04 -0400
> > From: Stefan Hajnoczi
> > Subject: Re: [PATCH] scripts/simpletrace: Mark output with unstable
&
On Wed, May 08, 2024 at 04:23:00PM +0200, Philippe Mathieu-Daudé wrote:
> Date: Wed, 8 May 2024 16:23:00 +0200
> From: Philippe Mathieu-Daudé
> Subject: Re: [PATCH] scripts/simpletrace: Mark output with unstable
> timestamp as WARN
>
> On 8/5/24 15:55, Zhao Liu wrot
On Wed, May 08, 2024 at 02:05:04PM -0400, Stefan Hajnoczi wrote:
> Date: Wed, 8 May 2024 14:05:04 -0400
> From: Stefan Hajnoczi
> Subject: Re: [PATCH] scripts/simpletrace: Mark output with unstable
> timestamp as WARN
>
> On Wed, 8 May 2024 at 00:19, Zhao Liu wrote:
> &g
On Wed, 8 May 2024 at 00:19, Zhao Liu wrote:
>
> In some trace log, there're unstable timestamp breaking temporal
> ordering of trace records. For example:
>
> kvm_run_exit -0.015 pid=3289596 cpu_index=0x0 reason=0x6
> kvm_vm_ioctl -0.020 pid=3289596 type=0xc008ae67 arg=0x7ffeefb5aa60
>
On 8/5/24 15:55, Zhao Liu wrote:
Hi Philippe,
On Wed, May 08, 2024 at 03:09:39PM +0200, Philippe Mathieu-Daudé wrote:
Date: Wed, 8 May 2024 15:09:39 +0200
From: Philippe Mathieu-Daudé
Subject: Re: [PATCH] scripts/simpletrace: Mark output with unstable
timestamp as WARN
On 8/5/24 06:32
Hi Philippe,
On Wed, May 08, 2024 at 03:09:39PM +0200, Philippe Mathieu-Daudé wrote:
> Date: Wed, 8 May 2024 15:09:39 +0200
> From: Philippe Mathieu-Daudé
> Subject: Re: [PATCH] scripts/simpletrace: Mark output with unstable
> timestamp as WARN
>
> On 8/5/24 06:32, Zhao Liu
On 8/5/24 06:32, Zhao Liu wrote:
In some trace log, there're unstable timestamp breaking temporal
ordering of trace records. For example:
kvm_run_exit -0.015 pid=3289596 cpu_index=0x0 reason=0x6
kvm_vm_ioctl -0.020 pid=3289596 type=0xc008ae67 arg=0x7ffeefb5aa60
kvm_vm_ioctl -0.021
In some trace log, there're unstable timestamp breaking temporal
ordering of trace records. For example:
kvm_run_exit -0.015 pid=3289596 cpu_index=0x0 reason=0x6
kvm_vm_ioctl -0.020 pid=3289596 type=0xc008ae67 arg=0x7ffeefb5aa60
kvm_vm_ioctl -0.021 pid=3289596 type=0xc008ae67
11 matches
Mail list logo
