From: David Woodhouse <dwmw2@infradead.org>
To: Ming Lin <minggr@gmail.com>
Cc: Sean Christopherson <seanjc@google.com>,
kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: pvclock time drifting backward
Date: Mon, 20 Apr 2026 18:26:49 +0100 [thread overview]
Message-ID: <e496fe0a05d9a4938f115207ff44f7a2c6500d22.camel@infradead.org> (raw)
In-Reply-To: <eaa33f756bc2e66ca193180a9847ee43fbdaa8ad.camel@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On Sat, 2025-03-29 at 08:20 +0000, David Woodhouse wrote:
> On Fri, 2025-03-28 at 11:30 -0700, Ming Lin wrote:
> > We are planning to test the patches on a 6.9 kernel (where they can be
> > applied cleanly) and modify the live upgrade/migration code to use the new
> > KVM_[GS]ET_CLOCK_GUEST ioctls.
> >
Did you?
> > BTW, what is the plan for upstreaming these patches?
>
> I need to find the time to rebase, rework and retest them. You're doing
> some of the testing and increasing the motivation... I'll see if I can
> get it done in the next week or three.
Heh, 'next week or three'. Sorry. But I have now made an initial pass, at
https://git.infradead.org/?p=users/dwmw2/linux.git;a=shortlog;h=refs/heads/kvmclock4
I've yet to give them a full review with human eyes; when I've done so
I should be reposting them.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5069 bytes --]
prev parent reply other threads:[~2026-04-20 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 5:38 Ming Lin
2025-03-24 22:54 ` Sean Christopherson
2025-03-25 11:07 ` David Woodhouse
2025-03-26 15:54 ` Ming Lin
2025-03-27 8:10 ` David Woodhouse
2025-03-28 18:30 ` Ming Lin
2025-03-29 8:20 ` David Woodhouse
2026-04-20 17:26 ` David Woodhouse [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=e496fe0a05d9a4938f115207ff44f7a2c6500d22.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minggr@gmail.com \
--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
all inboxes | Powered by JetHome®