From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37795) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Veno7-0005j5-Vf for qemu-devel@nongnu.org; Fri, 08 Nov 2013 10:17:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Veno0-0000gD-54 for qemu-devel@nongnu.org; Fri, 08 Nov 2013 10:17:11 -0500 Received: from mail-lb0-f181.google.com ([209.85.217.181]:59500) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vennz-0000eJ-UK for qemu-devel@nongnu.org; Fri, 08 Nov 2013 10:17:04 -0500 Received: by mail-lb0-f181.google.com with SMTP id x18so1596669lbi.12 for ; Fri, 08 Nov 2013 07:17:02 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <527CFE42.9090407@redhat.com> References: <1383859470.2527.64.camel@localhost.localdomain> <1383863039-18875-1-git-send-email-lersek@redhat.com> <1383863039-18875-2-git-send-email-lersek@redhat.com> <527CFE42.9090407@redhat.com> From: Peter Maydell Date: Fri, 8 Nov 2013 15:16:42 +0000 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [Qemu-devel] [PATCH 1/2] i386/pc: propagate flash size from pc_system_flash_init() to pc_init1() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek Cc: Marcel Apfelbaum , Jan Kiszka , "edk2-devel@lists.sourceforge.net" , qemu-devel , "Michael S. Tsirkin" , Anthony Liguori , Paolo Bonzini , Jordan Justen , afaerber , Richard Henderson On 8 November 2013 15:07, Laszlo Ersek wrote: > On 11/08/13 07:09, Jordan Justen wrote: >> int64_t? :) > > Heh, yes, I did cringe when I wrote that, but if you check the > bottom-most function, where the assignment happens, > pc_system_flash_init(), it declares the local "size" variable as > int64_t. I've given up on arguing for sensible unsigned types so I just > went with the flow That's a bug in that function which should be fixed. This is a memory region size and those are uint64_t. That said, having to pass the size of a sub-sub-region all the way back up the call stack is very odd and makes me wonder if it's really the right way to do it... The top level shouldn't have to care like that about details of the bottom of the callstack. thanks -- PMM