From: Paolo Bonzini <pbonzini@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Antoine Damhet <antoine.damhet@blade-group.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [PATCH] target/i386: always create kvmclock device
Date: Fri, 18 Sep 2020 10:39:38 +0200 [thread overview]
Message-ID: <3e22df90-fa06-bf88-70ca-04ec5047d96c@redhat.com> (raw)
In-Reply-To: <20200917174410.GU2793@work-vm>
On 17/09/20 19:44, Dr. David Alan Gilbert wrote:
>> This may happen with an older machine type when the destination is
>> running an unfixed QEMU and the source has the fix, right?
> Yes I think so.
>
>> The solution
>> would be to introduce a flag for older machine types (or for new ones)
>> like 'kvmclock_always'.
> Yep sounds the normal answer.
> (You might want to try it first to trigger the bug)
>
Right -- unqueued it :)
Paolo
next prev parent reply other threads:[~2020-09-18 8:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 11:13 [PATCH] target/i386: always create kvmclock device Vitaly Kuznetsov
2020-09-17 11:18 ` no-reply
2020-09-17 11:41 ` Vitaly Kuznetsov
2020-09-17 12:25 ` Antoine Damhet
2020-09-17 13:34 ` Vitaly Kuznetsov
2020-09-17 14:42 ` Dr. David Alan Gilbert
2020-09-17 14:58 ` Vitaly Kuznetsov
2020-09-17 17:44 ` Dr. David Alan Gilbert
2020-09-18 8:39 ` Paolo Bonzini [this message]
2020-09-18 15:12 ` Antoine Damhet
2020-09-18 15:26 ` Dr. David Alan Gilbert
2020-09-22 15:19 ` Vitaly Kuznetsov
2020-09-17 15:00 ` Antoine Damhet
2020-09-18 8:38 ` Paolo Bonzini
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=3e22df90-fa06-bf88-70ca-04ec5047d96c@redhat.com \
--to=pbonzini@redhat.com \
--cc=antoine.damhet@blade-group.com \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).