public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Miklos Szeredi <miklos@szeredi.hu>
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: Thu, 28 May 2020 22:43:02 +0200	[thread overview]
Message-ID: <875zcfoko9.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAJfpegstNYeseo_C4KOF9Y74qRxr78x2tK-9rTgmYM4CK30nRQ@mail.gmail.com>

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.

Thanks,

        tglx





  reply	other threads:[~2020-05-28 20:43 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 [this message]
2020-05-29  9:51   ` Miklos Szeredi
2020-05-29  9:57     ` Miklos Szeredi
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=875zcfoko9.fsf@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=jgross@suse.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=pbonzini@redhat.com \
    --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