From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH 0/2] PPC: Avoid temporary leaks
Date: Thu, 15 May 2014 18:34:16 +0200 [thread overview]
Message-ID: <5374EC88.5050606@suse.de> (raw)
In-Reply-To: <1400171295-20852-1-git-send-email-agraf@suse.de>
On 15.05.14 18:28, Alexander Graf wrote:
> Other targets have had it for quite a while, now PPC has it too! Temporary
> leakage tracking.
>
> Whenever we see that not all temporaries have been properly free'd at the
> end of a guest instruction block we can now scream loudly at the user.
>
> This hopefully ensures we don't leak as much as before :).
Oops - I missed that I already sent these patches before. I guess I can
just apply them straight ahead then. Sorry for the fuss :).
Alex
prev parent reply other threads:[~2014-05-15 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 16:28 [Qemu-devel] [PATCH 0/2] PPC: Avoid temporary leaks Alexander Graf
2014-05-15 16:28 ` [Qemu-devel] [PATCH 1/2] PPC: Fix TCG chunks that don't free their temps Alexander Graf
2014-05-15 16:28 ` [Qemu-devel] [PATCH 2/2] PPC: Fail on leaking temporaries Alexander Graf
2014-05-15 16:34 ` Alexander Graf [this message]
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=5374EC88.5050606@suse.de \
--to=agraf@suse.de \
--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).