From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Oliver Upton <oupton@google.com>,
Maxim Levitsky <mlevitsk@redhat.com>
Subject: Re: [PATCH] i386: Fix KVM_CAP_ADJUST_CLOCK capability check
Date: Fri, 07 Oct 2022 13:53:01 +0200 [thread overview]
Message-ID: <87pmf397fm.fsf@redhat.com> (raw)
In-Reply-To: <CABgObfaAFnnJDmgtsF69qUrayYf9+yg6GTX7wfCTkk1r1DkCdQ@mail.gmail.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> Hi, a similar patch is now in.
>
Indeed,
commit c4ef867f2949bf2a2ae18a4e27cf1a34bbc8aecb
Author: Ray Zhang <zhanglei002@gmail.com>
Date: Thu Sep 22 18:05:23 2022 +0800
target/i386/kvm: fix kvmclock_current_nsec: Assertion `time.tsc_timestamp <= migration_tsc' failed
solves the problem as well.
--
Vitaly
prev parent reply other threads:[~2022-10-07 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 14:40 [PATCH] i386: Fix KVM_CAP_ADJUST_CLOCK capability check Vitaly Kuznetsov
2022-09-20 18:33 ` Marcelo Tosatti
2022-09-27 9:45 ` Vitaly Kuznetsov
2022-10-07 9:26 ` Vitaly Kuznetsov
2022-10-07 10:49 ` Paolo Bonzini
2022-10-07 11:53 ` Vitaly Kuznetsov [this message]
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=87pmf397fm.fsf@redhat.com \
--to=vkuznets@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=mtosatti@redhat.com \
--cc=oupton@google.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).