From: Juan Quintela <quintela@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Glauber Costa <glommer@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: VMSTATE_U64 vs. VMSTATE_UINT64
Date: Mon, 09 May 2011 15:04:57 +0200 [thread overview]
Message-ID: <m3liyghvnq.fsf@neno.mitica> (raw)
In-Reply-To: <4DC19538.8010207@siemens.com> (Jan Kiszka's message of "Wed, 04 May 2011 20:04:40 +0200")
Jan Kiszka <jan.kiszka@siemens.com> wrote:
> Hi guys,
>
> can anyone comment on commit e4d6d49061 ("introduce VMSTATE_U64") in
> qemu-kvm again? I strongly suspect this thing was only introduced to be
> able to grab from a __u64 (for kvmclock) without generating a compiler
> warning that you may got when using uint64_t, right?
Yes, it was that on 64 bit u64 was unsigned long long and uint64_t was
only unsigned long or something like that. I have forgot if it was
kvmclock or irqchip also. I think that Marcelo also requested it at
some point, but dont' remember details :-(
Later, Juan.
prev parent reply other threads:[~2011-05-09 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 18:04 VMSTATE_U64 vs. VMSTATE_UINT64 Jan Kiszka
2011-05-04 18:16 ` Glauber Costa
2011-05-04 18:24 ` Jan Kiszka
2011-05-04 18:32 ` Trouble activating windows xp when booted with KVM Salame, Majid (Majid)
2011-05-04 19:44 ` VMSTATE_U64 vs. VMSTATE_UINT64 Glauber Costa
2011-05-09 13:04 ` Juan Quintela [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=m3liyghvnq.fsf@neno.mitica \
--to=quintela@redhat.com \
--cc=glommer@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.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