From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [Qemu-devel] [PATCH] Introduce QEMU_NEW() Date: Mon, 25 Jul 2011 17:21:26 +0200 Message-ID: <4E2D89F6.7060908@redhat.com> References: <1311583872-362-1-git-send-email-avi@redhat.com> <4E2D5D7C.40208@codemonkey.ws> <4E2D5F0D.2040303@redhat.com> <4E2D5FB3.7000906@codemonkey.ws> <4E2D82EF.4020606@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Anthony Liguori , Avi Kivity , qemu-devel@nongnu.org, kvm@vger.kernel.org To: Blue Swirl Return-path: Received: from mx1.redhat.com ([209.132.183.28]:64561 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751865Ab1GYPVc (ORCPT ); Mon, 25 Jul 2011 11:21:32 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 07/25/2011 04:56 PM, Blue Swirl wrote: > > qemu_malloc uses g_malloc => you keep tracepoints, you just do not trace > > memory allocated by glib > > Unless the plan is to replace all qemu_malloc() calls with calls to g_malloc(). We can worry when the day comes... there is already another task blocking that replacement (balancing qemu_malloc with qemu_free). > > The former is much less code, however it requires qemu_malloc to be always > > balanced with qemu_free (patches ready and on my github tree, won't be sent > > before KVM Forum though...). > > Freeing qemu_malloc() memory with plain free() is a bug. We have many bugs, then. :) Paolo