From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Kiszka <jan.kiszka@siemens.com>
Subject: VMSTATE_U64 vs. VMSTATE_UINT64
Date: Wed, 04 May 2011 20:04:40 +0200
Message-ID: <4DC19538.8010207@siemens.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit
Cc: kvm <kvm@vger.kernel.org>
To: Glauber Costa <glommer@redhat.com>,
	Juan Quintela <quintela@redhat.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from david.siemens.de ([192.35.17.14]:33689 "EHLO david.siemens.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1755116Ab1EDSEr (ORCPT <rfc822;kvm@vger.kernel.org>);
	Wed, 4 May 2011 14:04:47 -0400
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

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?

Thanks,
Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux