From: "Michael S. Tsirkin" <mst@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] port io mem leak
Date: Wed, 29 Feb 2012 18:39:26 +0200 [thread overview]
Message-ID: <20120229163925.GF8661@redhat.com> (raw)
In-Reply-To: <4F4E53FA.3090407@redhat.com>
On Wed, Feb 29, 2012 at 06:36:10PM +0200, Avi Kivity wrote:
> On 02/29/2012 06:18 PM, Anthony Liguori wrote:
> > On 02/29/2012 10:16 AM, Michael S. Tsirkin wrote:
> >> Valgrind shows a memory leak below:
> >
> > Is this with Avi's latest branch or is this in qemu.git?
>
> Looks like qemu.git.
This is a merge of your for-mst and my bridge patches.
Take a look at 'valgrind' branch on my github tree
if you like:
https://github.com/mstsirkin/qemu.git
> --
> error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-02-29 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 16:16 [Qemu-devel] port io mem leak Michael S. Tsirkin
2012-02-29 16:18 ` Anthony Liguori
2012-02-29 16:20 ` Michael S. Tsirkin
2012-02-29 16:36 ` Avi Kivity
2012-02-29 16:39 ` Michael S. Tsirkin [this message]
2012-02-29 16:40 ` Michael S. Tsirkin
2012-02-29 16:41 ` Avi Kivity
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=20120229163925.GF8661@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--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).