From: Miklos Szeredi <miklos@szeredi.hu>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Juergen Gross <jgross@suse.com>,
linux-kernel@vger.kernel.org
Subject: Re: system time goes weird in kvm guest after host suspend/resume
Date: Fri, 29 May 2020 11:57:45 +0200 [thread overview]
Message-ID: <CAJfpegv0fNfHrkovSXCNq5Hk+yHP7usfMgr0qjPfwqiovKygDA@mail.gmail.com> (raw)
In-Reply-To: <CAJfpegsjd+FJ0ZNHJ_qzJo0Dx22ZaWh-WZ48f94Z3AUXbJfYYQ@mail.gmail.com>
On Fri, May 29, 2020 at 11:51 AM Miklos Szeredi <miklos@szeredi.hu> wrote:
>
> On Thu, May 28, 2020 at 10:43 PM Thomas Gleixner <tglx@linutronix.de> wrote:
> >
> > Miklos Szeredi <miklos@szeredi.hu> writes:
> > > Bisected it to:
> > >
> > > b95a8a27c300 ("x86/vdso: Use generic VDSO clock mode storage")
> > >
> > > The effect observed is that after the host is resumed, the clock in
> > > the guest is somewhat in the future and is stopped. I.e. repeated
> > > date(1) invocations show the same time.
> >
> > TBH, the bisect does not make any sense at all. It's renaming the
> > constants and moving the storage space and I just read it line for line
> > again that the result is equivalent. I'll have a look once the merge
> > window dust settles a bit.
>
> Yet, reverting just that single commit against latest linus tree fixes
> the issue. Which I think is a pretty good indication that that commit
> *is* doing something.
>
> The jump forward is around 35 minutes; that seems to be consistent as well.
Oh, and here's a dmesg extract for the good case:
[ 26.402239] clocksource: timekeeping watchdog on CPU0: Marking
clocksource 'tsc' as unstable because the skew is too large:
[ 26.407029] clocksource: 'kvm-clock' wd_now:
635480f3c wd_last: 3ce94a718 mask: ffffffffffffffff
[ 26.407632] clocksource: 'tsc' cs_now:
92d2e5d08 cs_last: 81305ceee mask: ffffffffffffffff
[ 26.409097] tsc: Marking TSC unstable due to clocksource watchdog
and the bad one:
[ 36.667576] clocksource: timekeeping watchdog on CPU1: Marking
clocksource 'tsc' as unstable because the skew is too large:
[ 36.690441] clocksource: 'kvm-clock' wd_now:
89885027c wd_last: 3ea987282 mask: ffffffffffffffff
[ 36.690994] clocksource: 'tsc' cs_now:
95666ec22 cs_last: 84e747930 mask: ffffffffffffffff
[ 36.691901] tsc: Marking TSC unstable due to clocksource watchdog
Thanks,
Miklos
next prev parent reply other threads:[~2020-05-29 9:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 19:45 system time goes weird in kvm guest after host suspend/resume Miklos Szeredi
2020-05-28 20:43 ` Thomas Gleixner
2020-05-29 9:51 ` Miklos Szeredi
2020-05-29 9:57 ` Miklos Szeredi [this message]
2020-05-29 12:21 ` Thomas Gleixner
2020-05-29 12:31 ` Miklos Szeredi
2020-05-29 12:33 ` Miklos Szeredi
2020-06-03 15:41 ` Thomas Gleixner
2020-06-03 15:45 ` Thomas Gleixner
2020-06-04 17:30 ` Thomas Gleixner
2020-06-04 19:28 ` Miklos Szeredi
2020-06-04 20:14 ` Paolo Bonzini
2020-06-05 7:35 ` Miklos Szeredi
2020-06-05 8:09 ` Paolo Bonzini
2020-06-05 10:11 ` Thomas Gleixner
2020-06-05 10:21 ` Miklos Szeredi
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=CAJfpegv0fNfHrkovSXCNq5Hk+yHP7usfMgr0qjPfwqiovKygDA@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=jgross@suse.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.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;
as well as URLs for NNTP newsgroup(s).