From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alex Williamson Subject: Re: [Qemu-devel] Re: [PATCH] pc: e820 qemu_cfg tables need to be packed Date: Thu, 14 Oct 2010 13:58:08 -0600 Message-ID: <1287086288.2987.10.camel@x201> References: <20101014183249.23510.29196.stgit@s20.home> <4CB75D86.7040300@redhat.com> <4CB75EA4.9080004@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Jes Sorensen , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Anthony Liguori Return-path: Received: from mx1.redhat.com ([209.132.183.28]:31122 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755075Ab0JNT6P (ORCPT ); Thu, 14 Oct 2010 15:58:15 -0400 In-Reply-To: <4CB75EA4.9080004@codemonkey.ws> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, 2010-10-14 at 14:48 -0500, Anthony Liguori wrote: > On 10/14/2010 02:44 PM, Jes Sorensen wrote: > > On 10/14/10 20:33, Alex Williamson wrote: > > > >> We can't let the compiler define the alignment for qemu_cfg data. > >> > >> Signed-off-by: Alex Williamson > >> --- > >> > >> 0.13 stable candidate? > >> > > ACK I would say so. > > > > fw_cfg interfaces are somewhat difficult to rationalize about for > compatibility. > > 0.13.0 is tagged already so it's too late to pull it in there. If we > say we don't care about compatibility at the fw_cfg level, then it > doesn't matter if we pull it into stable-0.13. If we do care, then this > is an ABI breaker. If it works anywhere (I assume it works on 32bit), then it's only because it happened to get the alignment right. This just makes 64bit hosts get it right too. I don't see any compatibility issues, non-packed + 64bit = broken. Thanks, Alex