From: Marcelo Tosatti <mtosatti@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] kvmclock in wrong compat macro?
Date: Wed, 18 Jan 2017 15:54:03 -0200 [thread overview]
Message-ID: <20170118175359.GA6631@amt.cnet> (raw)
In-Reply-To: <20170118160308.GC2085@work-vm>
On Wed, Jan 18, 2017 at 04:03:08PM +0000, Dr. David Alan Gilbert wrote:
> Hi Marcelo,
> In commit 6053a86 'kvmclock: reduce kvmclock differences on migration'
> you add a 'x-mach-use-reliable-get-clock' and a compatibility entry
> that turns it off; if I'm reading it right though it got merged
> after 2.8.0 was released but the entry has gone into PC_COMPAT_2_7
> where I guess it should have gone into PC_COMPAT_2_8.
Hi David,
Thats right: there was a merge/time conflict (patch was written when
PC_COMPAT_2_8 made sense). Patch sent.
> Also, why is it x86 specific?
Because kvmclock is.
prev parent reply other threads:[~2017-01-20 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 16:03 [Qemu-devel] kvmclock in wrong compat macro? Dr. David Alan Gilbert
2017-01-18 17:54 ` Marcelo Tosatti [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=20170118175359.GA6631@amt.cnet \
--to=mtosatti@redhat.com \
--cc=dgilbert@redhat.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).