From: Glauber Costa <glommer@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH 1/3] introduce VMSTATE_U64
Date: Mon, 19 Oct 2009 22:38:11 -0200 [thread overview]
Message-ID: <20091020003810.GY8092@mothafucka.localdomain> (raw)
In-Reply-To: <4ADCF8EA.4060608@redhat.com>
On Tue, Oct 20, 2009 at 08:40:26AM +0900, Avi Kivity wrote:
> On 10/17/2009 04:27 AM, Glauber Costa wrote:
>> This is a patch actually written by Juan, which, according to him,
>> he plans on posting to qemu.git. Problem is that linux defines
>> u64 in a way that is type-uncompatible with uint64_t.
>>
>> I am including it here, because it is a dependency to my patch series
>> that follows.
>>
>>
>
> Why can't we store these values in qemu as uint64_ts?
Because then we have to redefine the whole structure in qemu.
the proposal is to simply pick the structures directly from linux. I believe
it is much easier, and the versioning scheme in vmstate will help us get
around any changes they might suffer in the future.
next prev parent reply other threads:[~2009-10-20 0:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 19:27 [PATCH 0/3] Fix migration of linux guests using kvmclock Glauber Costa
2009-10-16 19:27 ` [PATCH 1/3] introduce VMSTATE_U64 Glauber Costa
2009-10-16 19:27 ` [PATCH 2/3] properly save kvm system time msr registers Glauber Costa
2009-10-16 19:27 ` [PATCH 3/3] get and set clock upon migration Glauber Costa
2009-10-19 23:40 ` [PATCH 1/3] introduce VMSTATE_U64 Avi Kivity
2009-10-20 0:38 ` Glauber Costa [this message]
2009-10-19 19:51 ` [PATCH 0/3] Fix migration of linux guests using kvmclock Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
2009-10-27 17:49 [PATCH 1/3] introduce VMSTATE_U64 Andrew Theurer
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=20091020003810.GY8092@mothafucka.localdomain \
--to=glommer@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=quintela@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