public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Sean Christopherson <seanjc@google.com>,
	kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: David Woodhouse <dwmw@amazon.co.uk>,
	Jan Richter <jarichte@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: selftests: Compare wall time from xen shinfo against KVM_GET_CLOCK
Date: Sat, 03 Feb 2024 00:27:45 +0100	[thread overview]
Message-ID: <87r0huh2fi.fsf@redhat.com> (raw)
In-Reply-To: <ZbvObrzoyZlay-Xg@google.com>

Sean Christopherson <seanjc@google.com> writes:

> On Tue, Jan 30, 2024, Sean Christopherson wrote:
>> On Thu, 11 Jan 2024 14:59:01 +0100, Vitaly Kuznetsov wrote:
>> > xen_shinfo_test is observed to be flaky failing sporadically with
>> > "VM time too old". With min_ts/max_ts debug print added:
>> > 
>> > Wall clock (v 3269818) 1704906491.986255664
>> > Time info 1: v 1282712 tsc 33530585736 time 14014430025 mul 3587552223 shift 4294967295 flags 1
>> > Time info 2: v 1282712 tsc 33530585736 time 14014430025 mul 3587552223 shift 4294967295 flags 1
>> > min_ts: 1704906491.986312153
>> > max_ts: 1704906506.001006963
>> > ==== Test Assertion Failure ====
>> >   x86_64/xen_shinfo_test.c:1003: cmp_timespec(&min_ts, &vm_ts) <= 0
>> >   pid=32724 tid=32724 errno=4 - Interrupted system call
>> >      1	0x00000000004030ad: main at xen_shinfo_test.c:1003
>> >      2	0x00007fca6b23feaf: ?? ??:0
>> >      3	0x00007fca6b23ff5f: ?? ??:0
>> >      4	0x0000000000405e04: _start at ??:?
>> >   VM time too old
>> > 
>> > [...]
>> 
>> Applied to kvm-x86 selftests.  David, please holler if you disagree with
>> any of the changes.  They look sane to me, but clock stuff ain't my forte.
>> 
>> Thanks!
>> 
>> [1/1] KVM: selftests: Compare wall time from xen shinfo against KVM_GET_CLOCK
>>       https://github.com/kvm-x86/linux/commit/a0868e7c5575
>
> FYI, I've dropped this as it looks like there will be a new version.

Thanks, indeed, I'll do do changes suggested by David in v2 but as I'm
traveling this weekend (FOSDEM calls!) please expect my posting Tuesday+
next week.

-- 
Vitaly


  reply	other threads:[~2024-02-02 23:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-11 13:59 [PATCH] KVM: selftests: Compare wall time from xen shinfo against KVM_GET_CLOCK Vitaly Kuznetsov
2024-01-29  9:04 ` Vitaly Kuznetsov
2024-01-29 16:06   ` Sean Christopherson
2024-01-31  0:59 ` Sean Christopherson
2024-02-01 17:01   ` Sean Christopherson
2024-02-02 23:27     ` Vitaly Kuznetsov [this message]
2024-01-31 16:34 ` David Woodhouse
2024-02-01 10:19   ` Vitaly Kuznetsov
2024-02-01 16:02     ` David Woodhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0huh2fi.fsf@redhat.com \
    --to=vkuznets@redhat.com \
    --cc=dwmw@amazon.co.uk \
    --cc=jarichte@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=seanjc@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox