From: Shivaprasad G Bhat <sbhat@linux.ibm.com>
To: qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v2 0/4] ppc: Fix some memory leaks
Date: Wed, 17 Jul 2019 03:19:15 -0500 [thread overview]
Message-ID: <156335150620.82682.9535735857478533420.stgit@lep8c.aus.stglabs.ibm.com> (raw)
Valgrind showed some memory leaks while running qemu-system-ppc64.
Fixing them in this series.
---
Shivaprasad G Bhat (4):
ppc: fix memory leak in spapr_caps_add_properties
ppc: fix memory leak in spapr_dt_drc()
ppc: fix leak in h_client_architecture_support
ppc: dont overwrite initialized idle_timer
hw/ppc/spapr_caps.c | 4 +++-
hw/ppc/spapr_drc.c | 7 +++++--
hw/ppc/spapr_hcall.c | 2 ++
target/ppc/kvm.c | 3 ++-
4 files changed, 12 insertions(+), 4 deletions(-)
--
Signature
next reply other threads:[~2019-07-17 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 8:19 Shivaprasad G Bhat [this message]
2019-07-17 8:19 ` [Qemu-devel] [PATCH v2 1/4] ppc: fix memory leak in spapr_caps_add_properties Shivaprasad G Bhat
2019-07-17 10:41 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2019-07-18 4:19 ` [Qemu-devel] " David Gibson
2019-07-17 8:20 ` [Qemu-devel] [PATCH v2 2/4] ppc: fix memory leak in spapr_dt_drc() Shivaprasad G Bhat
2019-07-17 10:47 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2019-07-18 4:20 ` [Qemu-devel] " David Gibson
2019-07-17 8:20 ` [Qemu-devel] [PATCH v2 3/4] ppc: fix leak in h_client_architecture_support Shivaprasad G Bhat
2019-07-17 10:47 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2019-07-18 4:21 ` [Qemu-devel] " David Gibson
2019-07-17 8:20 ` [Qemu-devel] [PATCH v2 4/4] ppc: dont overwrite initialized idle_timer Shivaprasad G Bhat
2019-07-17 14:58 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
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=156335150620.82682.9535735857478533420.stgit@lep8c.aus.stglabs.ibm.com \
--to=sbhat@linux.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).