From: Stefan Weil <sw@weilnetz.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/3] Fix some memory leaks caused by qemu_allocate_irqs
Date: Mon, 24 Sep 2012 21:08:47 +0200 [thread overview]
Message-ID: <1348513730-7485-1-git-send-email-sw@weilnetz.de> (raw)
There are several memory leaks in QEMU which are caused by calling
qemu_allocate_irqs.
Some of these leaks are fixed here in the 2nd and 3rd patch.
More can be fixed using the same pattern.
The first patch adds a new function which avoids unnecessary
memory allocation.
[PATCH 1/3] irq: Add new function qemu_init_irqs
[PATCH 2/3] hw/arm_timer: Fix memory leak (detected by Valgrind)
[PATCH 3/3] hw/spitz: Fix memory leaks (detected by Valgrind)
Regards
Stefan Weil
next reply other threads:[~2012-09-24 19:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 19:08 Stefan Weil [this message]
2012-09-24 19:08 ` [Qemu-devel] [PATCH 1/3] irq: Add new function qemu_init_irqs Stefan Weil
2012-09-24 19:26 ` Peter Maydell
2012-09-24 19:08 ` [Qemu-devel] [PATCH 2/3] hw/arm_timer: Fix memory leak (detected by Valgrind) Stefan Weil
2012-09-24 19:08 ` [Qemu-devel] [PATCH 3/3] hw/spitz: Fix memory leaks " Stefan Weil
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=1348513730-7485-1-git-send-email-sw@weilnetz.de \
--to=sw@weilnetz.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).