From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 1/3] introduce VMSTATE_U64 Date: Tue, 20 Oct 2009 08:40:26 +0900 Message-ID: <4ADCF8EA.4060608@redhat.com> References: <1255721259-11740-1-git-send-email-glommer@redhat.com> <1255721259-11740-2-git-send-email-glommer@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Juan Quintela To: Glauber Costa Return-path: Received: from mx1.redhat.com ([209.132.183.28]:48308 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756069AbZJSXkZ (ORCPT ); Mon, 19 Oct 2009 19:40:25 -0400 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n9JNeUch027130 for ; Mon, 19 Oct 2009 19:40:30 -0400 In-Reply-To: <1255721259-11740-2-git-send-email-glommer@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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? -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.