From: Steven Haigh <netwiz@crc.id.au>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: Possible memory leak in qemu-dm (qemu-dm swapping 20GB+, adding 2gb+ per day)
Date: Tue, 25 Mar 2014 21:48:05 +1100 [thread overview]
Message-ID: <53315EE5.7050803@crc.id.au> (raw)
In-Reply-To: <1395743334.6294.37.camel@kazak.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1119 bytes --]
On 25/03/14 21:28, Ian Campbell wrote:
> On Tue, 2014-03-25 at 09:09 +0200, Pasi Kärkkäinen wrote:
>> On Tue, Mar 25, 2014 at 01:08:00PM +1100, Steven Haigh wrote:
>>> Continuing from:
>>> http://lists.xenproject.org/archives/html/xen-devel/2013-11/msg03961.html
>>>
>>> Hi guys,
>>>
>>> Continuing on from this thread, has any progress been made on this?
>>>
>>> I have had a report from a user of my packages with the same problem:
>>> http://xen.crc.id.au/bugs/view.php?id=25
>>>
>>> He has been able to reproduce this in a reliable manner.
>>>
>>
>> I thought the fix was committed to all the maintained qemu-traditional branches..
>
> I think so too.
>
> But if not then given a reliable repro I think the advice to try it
> under valgrind (which AIUI can now traces qemus thanks to Andrew Coopers
> work) still holds as a useful next step.
Is there any guide on how to do this to gather said info? Documentation?
Implementation? Interpretation?
--
Steven Haigh
Email: netwiz@crc.id.au
Web: https://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-03-25 10:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 2:08 Possible memory leak in qemu-dm (qemu-dm swapping 20GB+, adding 2gb+ per day) Steven Haigh
2014-03-25 7:09 ` Pasi Kärkkäinen
2014-03-25 10:28 ` Ian Campbell
2014-03-25 10:48 ` Steven Haigh [this message]
2014-03-25 11:03 ` Ian Campbell
2014-03-25 11:16 ` Andrew Cooper
2014-03-26 5:23 ` Steven Haigh
2014-03-26 8:57 ` Ian Campbell
2014-03-26 9:09 ` Steven Haigh
2014-03-26 9:41 ` Ian Campbell
2014-03-26 15:01 ` Pasi Kärkkäinen
2014-03-26 23:49 ` Steven Haigh
-- strict thread matches above, loose matches on Subject: below --
2013-11-20 14:57 Niklas Bivald
2013-11-22 1:49 ` Matthew Daley
2013-11-25 9:48 ` Niklas Bivald
2013-11-25 11:58 ` Ian Jackson
2013-11-25 12:32 ` Niklas Bivald
2013-11-25 12:40 ` Ian Jackson
2013-11-25 12:59 ` Niklas Bivald
2013-11-27 9:49 ` Niklas Bivald
2013-11-27 10:32 ` Fabio Fantoni
2013-11-27 11:06 ` Ian Campbell
2013-12-02 20:49 ` Niklas Bivald
2013-12-02 22:24 ` Matthew Daley
2013-12-03 8:27 ` Niklas Bivald
2013-12-03 11:10 ` Ian Campbell
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=53315EE5.7050803@crc.id.au \
--to=netwiz@crc.id.au \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xen.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 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.