From: Sean Christopherson <seanjc@google.com>
To: "Jayaramappa, Srilakshmi" <sjayaram@akamai.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"mlevitsk@redhat.com" <mlevitsk@redhat.com>,
"suleiman@google.com" <suleiman@google.com>,
"Hunt, Joshua" <johunt@akamai.com>
Subject: Re: KVM: x86: snapshotted TSC frequency causing time drifts in vms
Date: Wed, 14 Dec 2022 23:58:11 +0000 [thread overview]
Message-ID: <Y5pjEwsdeRXVtjcj@google.com> (raw)
In-Reply-To: <46774ef6c59e45bf9b166ca4833dddd7@akamai.com>
On Wed, Dec 14, 2022, Jayaramappa, Srilakshmi wrote:
> > There doesn't seem to be any response on the v6 of Anton's patch. I wanted to
> > ask if there is further changes in progress or if it is all set to be merged?
>
> Drat, it slipped through the cracks.
>
> Paolo, can you pick up the below patch? Oobviously assuming you don't spy any
> problems.
>
> It has a superficial conflict with commit 938c8745bcf2 ("KVM: x86: Introduce
...
> Could I trouble you to take a look at this patch please?
It's already in kvm/next
3ebcbd2244f5 ("KVM: x86: Use current rather than snapshotted TSC frequency if it is constant")
but there was a hiccup with the KVM pull request for 6.2[*], which is why it hasn't
made it's way to Linus yet.
[*] https://lore.kernel.org/all/6d96a62e-d5a1-e606-3bd2-c38f4a6c8545@redhat.com
next prev parent reply other threads:[~2022-12-15 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 18:35 KVM: x86: snapshotted TSC frequency causing time drifts in vms Jayaramappa, Srilakshmi
2022-10-31 21:59 ` Sean Christopherson
2022-10-31 23:00 ` Jayaramappa, Srilakshmi
2022-12-14 21:24 ` Jayaramappa, Srilakshmi
2022-12-14 23:58 ` Sean Christopherson [this message]
2022-12-15 0:46 ` Jayaramappa, Srilakshmi
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=Y5pjEwsdeRXVtjcj@google.com \
--to=seanjc@google.com \
--cc=johunt@akamai.com \
--cc=kvm@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=sjayaram@akamai.com \
--cc=suleiman@google.com \
--cc=vkuznets@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.