From: Glauber Costa <glommer@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] save kvm-specific msrs over save/load
Date: Tue, 13 Oct 2009 09:29:55 -0300 [thread overview]
Message-ID: <20091013122955.GA8092@mothafucka.localdomain> (raw)
In-Reply-To: <4AD33B73.3020808@codemonkey.ws>
On Mon, Oct 12, 2009 at 09:21:39AM -0500, Anthony Liguori wrote:
> Glauber Costa wrote:
>> Although we currently do not register a pvclock, there is no harm in saving the
>> values of the involved msrs. We'll just load an empty value. qemu-kvm, OTOH,
>> will make the correct use of it, so I think it is better to do it here, than
>> to augment the diff.
>>
>
> How does the cpu versioning match up with qemu-kvm?
>
> Has this gone into the qemu-kvm tree yet?
No. I opted by sendind it here first.
I can do the very opposite, however, if you prefer. Just let me know.
>
> We've already bumped the version once for the 0.12 release so it's not
> necessary to bump it again.
okay.
prev parent reply other threads:[~2009-10-13 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 18:35 [Qemu-devel] [PATCH] save kvm-specific msrs over save/load Glauber Costa
2009-10-12 14:21 ` Anthony Liguori
2009-10-13 12:29 ` Glauber Costa [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=20091013122955.GA8092@mothafucka.localdomain \
--to=glommer@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@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).