From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MszNA-0005ur-NW for qemu-devel@nongnu.org; Wed, 30 Sep 2009 09:37:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MszN7-0005oX-4h for qemu-devel@nongnu.org; Wed, 30 Sep 2009 09:37:36 -0400 Received: from [199.232.76.173] (port=52512 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MszN6-0005oJ-PN for qemu-devel@nongnu.org; Wed, 30 Sep 2009 09:37:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:21964) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MszN6-0003Xz-8m for qemu-devel@nongnu.org; Wed, 30 Sep 2009 09:37:32 -0400 From: Juan Quintela In-Reply-To: (malc's message of "Wed, 30 Sep 2009 17:12:26 +0400 (MSD)") References: Date: Wed, 30 Sep 2009 15:37:05 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: [Qemu-devel] Re: [PATCH 27/49] ac97: add active to the state List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: malc Cc: qemu-devel@nongnu.org malc wrote: >> >> There are more temporary variables in other devices, and this was the >> >> way it was done there. Normally I would have called it active_vmstate >> >> to make that explicit, but here, it was also used for reset, that is the >> >> way I named it with the _vmstate suffix. >> > >> > In any case the while i can understand the fear of malloc, nobody forces >> > you to do that you can have a scratch space on the stack, with an some >> > upper cap, that's the way it's done now anyhow, only the cap is stack size >> > reserved for the process and not something you have to choose. >> >> You call new way a monstrosity, and now propose a solution that makes >> the monster bigger? >> >> I still stand behind the patch, and I still want it applied. >> > > And it wont be, not this part of it, not in this state. Suggestions? Because you are not telling me that you expect to move something to the stack, reimplement alloca() and work from there was a _real suggestion_? Later, Juan.