All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, mreitz@redhat.com, kwolf@redhat.com,
	vsementsov@virtuozzo.com, jsnow@redhat.com, eesposit@redhat.com,
	pbonzini@redhat.com, eblake@redhat.com, stefanha@redhat.com
Subject: [PATCH 1/2] introduce QEMU_AUTO_VFREE
Date: Sat, 19 Jun 2021 17:21:19 +0300	[thread overview]
Message-ID: <20210619142120.48211-2-vsementsov@virtuozzo.com> (raw)
In-Reply-To: <20210619142120.48211-1-vsementsov@virtuozzo.com>

Introduce a convenient macro, that works for qemu_memalign() like
g_autofree works with g_malloc.

Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
---
 include/qemu/osdep.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/qemu/osdep.h b/include/qemu/osdep.h
index 236a045671..844658a764 100644
--- a/include/qemu/osdep.h
+++ b/include/qemu/osdep.h
@@ -366,6 +366,8 @@ void *qemu_anon_ram_alloc(size_t size, uint64_t *align, bool shared);
 void qemu_vfree(void *ptr);
 void qemu_anon_ram_free(void *ptr, size_t size);
 
+#define QEMU_AUTO_VFREE __attribute__((cleanup(qemu_vfree)))
+
 #define QEMU_MADV_INVALID -1
 
 #if defined(CONFIG_MADVISE)
-- 
2.29.2



  reply	other threads:[~2021-06-19 14:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19 14:21 [PATCH 0/2] introduce QEMU_AUTO_VFREE Vladimir Sementsov-Ogievskiy
2021-06-19 14:21 ` Vladimir Sementsov-Ogievskiy [this message]
2021-06-19 14:21 ` [PATCH 2/2] block/commit: use QEMU_AUTO_VFREE Vladimir Sementsov-Ogievskiy
2021-06-21 13:33 ` [PATCH 0/2] introduce QEMU_AUTO_VFREE Stefan Hajnoczi
2021-06-23 10:34 ` Kevin Wolf
2021-06-28 10:08   ` Kevin Wolf
2021-06-28 11:39     ` Vladimir Sementsov-Ogievskiy

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=20210619142120.48211-2-vsementsov@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=eblake@redhat.com \
    --cc=eesposit@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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.