From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58123) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJNXP-0001K7-8t for qemu-devel@nongnu.org; Thu, 05 Feb 2015 09:36:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YJNXM-0004ZJ-4s for qemu-devel@nongnu.org; Thu, 05 Feb 2015 09:36:11 -0500 Received: from mx1.redhat.com ([209.132.183.28]:48594) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJNXL-0004Z7-TF for qemu-devel@nongnu.org; Thu, 05 Feb 2015 09:36:08 -0500 Message-ID: <54D37FC9.1040506@redhat.com> Date: Thu, 05 Feb 2015 16:35:53 +0200 From: Marcel Apfelbaum MIME-Version: 1.0 References: <20150123132424.GA4579@redhat.com> <20150123144030.21142ed1@nial.brq.redhat.com> <20150123135511.GF4579@redhat.com> <20150123185620.604b83ab@nial.brq.redhat.com> <20150124163350.GC6293@redhat.com> <20150126105721.60641e59@nial.brq.redhat.com> <20150126160920.79a09b37@nial.brq.redhat.com> <20150126153400.GB3536@hawk.usersys.redhat.com> <20150126161755.GA5487@redhat.com> <20150127232909.6c045626@igors-macbook-pro.local> <20150128075626.GA16660@redhat.com> <20150128110023.160e5d24@nial.brq.redhat.com> In-Reply-To: <20150128110023.160e5d24@nial.brq.redhat.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v2 01/47] acpi: introduce AML composer aml_append() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Igor Mammedov , "Michael S. Tsirkin" Cc: Andrew Jones , marcel.a@redhat.com, claudio.fontana@huawei.com, qemu-devel@nongnu.org, Shannon Zhao , pbonzini@redhat.com On 01/28/2015 12:00 PM, Igor Mammedov wrote: > On Wed, 28 Jan 2015 09:56:26 +0200 [...] > > Hence is suggesting at least to hide AmlPool internally in API > without exposing it to user. We can provide for user > init/free API to manage internal AmlPool manually, allowing > him to select when to do initialization and cleanup. This I like the most. > > Claudio, Marcel, Shannon, > As the first API users, could you give your feedback on the topic. As a happy API user, I really like it as it is. Since we do need to address the allocation/freeing issues I like the internal AmlPool as I stated already in a few places :) Thanks, Marcel >