From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH] Introduce QEMU_NEW()
Date: Mon, 25 Jul 2011 15:18:21 +0300 [thread overview]
Message-ID: <4E2D5F0D.2040303@redhat.com> (raw)
In-Reply-To: <4E2D5D7C.40208@codemonkey.ws>
On 07/25/2011 03:11 PM, Anthony Liguori wrote:
> On 07/25/2011 03:51 AM, Avi Kivity wrote:
>> qemu_malloc() is type-unsafe as it returns a void pointer. Introduce
>> QEMU_NEW() (and QEMU_NEWZ()), which return the correct type.
>
> Just use g_new() and g_new0()
>
These bypass qemu_malloc(). Are we okay with that?
I suppose so, since many library functions can allocate memory and
bypass qemu_malloc()?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-07-25 12:18 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 8:51 [PATCH] Introduce QEMU_NEW() Avi Kivity
2011-07-25 8:51 ` [Qemu-devel] " Avi Kivity
2011-07-25 9:32 ` Alexander Graf
2011-07-25 9:32 ` [Qemu-devel] " Alexander Graf
2011-07-25 9:37 ` Sasha Levin
2011-07-25 9:37 ` [Qemu-devel] " Sasha Levin
2011-07-25 9:43 ` Alexander Graf
2011-07-25 9:43 ` [Qemu-devel] " Alexander Graf
2011-07-25 9:49 ` Avi Kivity
2011-07-25 9:49 ` [Qemu-devel] " Avi Kivity
2011-07-25 9:48 ` Peter Maydell
2011-07-25 9:48 ` Peter Maydell
2011-07-25 9:52 ` Avi Kivity
2011-07-25 9:52 ` Avi Kivity
2011-07-25 9:56 ` Alexander Graf
2011-07-25 9:56 ` [Qemu-devel] " Alexander Graf
2011-07-25 10:02 ` Avi Kivity
2011-07-25 10:02 ` [Qemu-devel] " Avi Kivity
2011-07-25 10:04 ` Alexander Graf
2011-07-25 10:09 ` Avi Kivity
2011-07-25 10:19 ` Alexander Graf
2011-07-25 10:19 ` [Qemu-devel] " Alexander Graf
2011-07-25 10:46 ` malc
2011-07-25 10:46 ` malc
2011-07-25 10:59 ` Markus Armbruster
2011-07-25 10:59 ` [Qemu-devel] " Markus Armbruster
2011-07-25 11:11 ` Alexander Graf
2011-07-25 11:11 ` Alexander Graf
2011-07-25 12:19 ` Anthony Liguori
2011-07-25 12:19 ` Anthony Liguori
2011-07-25 14:16 ` Blue Swirl
2011-07-25 14:16 ` Blue Swirl
2011-07-25 14:20 ` Avi Kivity
2011-07-25 14:20 ` [Qemu-devel] " Avi Kivity
2011-07-25 12:30 ` Anthony Liguori
2011-07-25 11:35 ` Avi Kivity
2011-07-25 11:35 ` [Qemu-devel] " Avi Kivity
2011-07-25 10:06 ` Stefan Hajnoczi
2011-07-25 10:06 ` [Qemu-devel] " Stefan Hajnoczi
2011-07-25 10:12 ` Avi Kivity
2011-07-25 10:25 ` Kevin Wolf
2011-07-25 10:25 ` Kevin Wolf
2011-07-25 10:28 ` Stefan Hajnoczi
2011-07-25 10:28 ` Stefan Hajnoczi
2011-07-25 11:02 ` Markus Armbruster
2011-07-25 11:02 ` Markus Armbruster
2011-07-25 11:45 ` Avi Kivity
2011-07-25 15:10 ` Jes Sorensen
2011-07-25 15:10 ` [Qemu-devel] " Jes Sorensen
2011-07-25 15:15 ` Anthony Liguori
2011-07-25 15:17 ` Jes Sorensen
2011-07-25 15:20 ` Avi Kivity
2011-07-25 15:20 ` [Qemu-devel] " Avi Kivity
2011-07-25 15:21 ` Jes Sorensen
2011-07-25 15:21 ` Jes Sorensen
2011-07-25 15:24 ` Avi Kivity
2011-07-25 15:24 ` [Qemu-devel] " Avi Kivity
2011-07-25 15:28 ` Jes Sorensen
2011-07-25 15:28 ` Jes Sorensen
2011-07-25 15:35 ` Avi Kivity
2011-07-25 15:35 ` [Qemu-devel] " Avi Kivity
2011-07-25 12:11 ` Anthony Liguori
2011-07-25 12:11 ` [Qemu-devel] " Anthony Liguori
2011-07-25 12:18 ` Avi Kivity [this message]
2011-07-25 12:21 ` Anthony Liguori
2011-07-25 12:41 ` Avi Kivity
2011-07-25 12:41 ` [Qemu-devel] " Avi Kivity
2011-07-25 14:23 ` Blue Swirl
2011-07-25 14:23 ` Blue Swirl
2011-07-25 14:25 ` Anthony Liguori
2011-07-25 14:30 ` Max Filippov
2011-07-25 14:30 ` [Qemu-devel] " Max Filippov
2011-07-25 14:43 ` Anthony Liguori
2011-07-25 14:47 ` malc
2011-07-25 14:47 ` [Qemu-devel] " malc
2011-07-25 14:50 ` Avi Kivity
2011-07-25 14:50 ` Avi Kivity
2011-07-25 14:58 ` malc
2011-07-25 14:58 ` malc
2011-07-25 14:59 ` Avi Kivity
2011-07-25 14:59 ` Avi Kivity
2011-07-25 14:51 ` Paolo Bonzini
2011-07-25 14:51 ` Paolo Bonzini
2011-07-25 14:56 ` Blue Swirl
2011-07-25 14:56 ` Blue Swirl
2011-07-25 15:21 ` Paolo Bonzini
2011-07-25 15:21 ` Paolo Bonzini
2011-08-01 10:49 ` Richard W.M. Jones
2011-08-01 10:49 ` Richard W.M. Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E2D5F0D.2040303@redhat.com \
--to=avi@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.