From: "Christian König" <christian.koenig@amd.com>
To: Eli Cohen <elic@nvidia.com>
Cc: daniel.vetter@ffwll.ch, linux-kernel@vger.kernel.org,
dri-devel <dri-devel@lists.freedesktop.org>,
virtualization@lists.linux-foundation.org,
Thomas Zimmermann <tzimmermann@suse.de>,
sam@ravnborg.org
Subject: Re: Change eats memory on my server
Date: Mon, 18 Jan 2021 08:57:26 +0100 [thread overview]
Message-ID: <a39c1b62-3e22-2454-d68b-e9eb510891d3@amd.com> (raw)
In-Reply-To: <20210118074913.GA39161@mtl-vdi-166.wap.labs.mlnx>
Am 18.01.21 um 08:49 schrieb Eli Cohen:
> On Mon, Jan 18, 2021 at 08:43:12AM +0100, Christian König wrote:
>> Hi Eli,
>>
>> have you already tried using kmemleak?
>>
>> This sounds like a leak of memory allocated using kmalloc(), so kmemleak
>> should be able to catch it.
>>
> Hi Christian,
>
> I have the following configured but I did not see any visible complaint
> in dmesg.
>
> CONFIG_HAVE_DEBUG_KMEMLEAK=y
> CONFIG_DEBUG_KMEMLEAK=y
> CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE=16000
>
> Any other configuration that I need to set?
As long as you don't have any kernel parameters to enable it I think you
need to do "echo scan > /sys/kernel/debug/kmemleak" to start a scan.
The result can then be queried using "cat /sys/kernel/debug/kmemleak".
Regards,
Christian.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <christian.koenig@amd.com>
To: Eli Cohen <elic@nvidia.com>
Cc: daniel.vetter@ffwll.ch, linux-kernel@vger.kernel.org,
dri-devel <dri-devel@lists.freedesktop.org>,
virtualization@lists.linux-foundation.org,
Thomas Zimmermann <tzimmermann@suse.de>,
sam@ravnborg.org
Subject: Re: Change eats memory on my server
Date: Mon, 18 Jan 2021 08:57:26 +0100 [thread overview]
Message-ID: <a39c1b62-3e22-2454-d68b-e9eb510891d3@amd.com> (raw)
In-Reply-To: <20210118074913.GA39161@mtl-vdi-166.wap.labs.mlnx>
Am 18.01.21 um 08:49 schrieb Eli Cohen:
> On Mon, Jan 18, 2021 at 08:43:12AM +0100, Christian König wrote:
>> Hi Eli,
>>
>> have you already tried using kmemleak?
>>
>> This sounds like a leak of memory allocated using kmalloc(), so kmemleak
>> should be able to catch it.
>>
> Hi Christian,
>
> I have the following configured but I did not see any visible complaint
> in dmesg.
>
> CONFIG_HAVE_DEBUG_KMEMLEAK=y
> CONFIG_DEBUG_KMEMLEAK=y
> CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE=16000
>
> Any other configuration that I need to set?
As long as you don't have any kernel parameters to enable it I think you
need to do "echo scan > /sys/kernel/debug/kmemleak" to start a scan.
The result can then be queried using "cat /sys/kernel/debug/kmemleak".
Regards,
Christian.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: "Christian König" <christian.koenig@amd.com>
To: Eli Cohen <elic@nvidia.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, daniel.vetter@ffwll.ch,
sam@ravnborg.org, dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Change eats memory on my server
Date: Mon, 18 Jan 2021 08:57:26 +0100 [thread overview]
Message-ID: <a39c1b62-3e22-2454-d68b-e9eb510891d3@amd.com> (raw)
In-Reply-To: <20210118074913.GA39161@mtl-vdi-166.wap.labs.mlnx>
Am 18.01.21 um 08:49 schrieb Eli Cohen:
> On Mon, Jan 18, 2021 at 08:43:12AM +0100, Christian König wrote:
>> Hi Eli,
>>
>> have you already tried using kmemleak?
>>
>> This sounds like a leak of memory allocated using kmalloc(), so kmemleak
>> should be able to catch it.
>>
> Hi Christian,
>
> I have the following configured but I did not see any visible complaint
> in dmesg.
>
> CONFIG_HAVE_DEBUG_KMEMLEAK=y
> CONFIG_DEBUG_KMEMLEAK=y
> CONFIG_DEBUG_KMEMLEAK_MEM_POOL_SIZE=16000
>
> Any other configuration that I need to set?
As long as you don't have any kernel parameters to enable it I think you
need to do "echo scan > /sys/kernel/debug/kmemleak" to start a scan.
The result can then be queried using "cat /sys/kernel/debug/kmemleak".
Regards,
Christian.
next prev parent reply other threads:[~2021-01-18 7:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 15:15 Change eats memory on my server Eli Cohen
2021-01-15 9:03 ` Thomas Zimmermann
2021-01-15 9:03 ` Thomas Zimmermann
2021-01-15 9:03 ` Thomas Zimmermann
2021-01-17 5:08 ` Eli Cohen
2021-01-17 5:08 ` Eli Cohen
2021-01-18 7:43 ` Christian König
2021-01-18 7:43 ` Christian König
2021-01-18 7:43 ` Christian König
2021-01-18 7:49 ` Eli Cohen
2021-01-18 7:49 ` Eli Cohen
2021-01-18 7:57 ` Christian König [this message]
2021-01-18 7:57 ` Christian König
2021-01-18 7:57 ` Christian König
2021-01-18 9:12 ` Eli Cohen
2021-01-18 9:12 ` Eli Cohen
2021-01-18 7:54 ` Thomas Zimmermann
2021-01-18 7:54 ` Thomas Zimmermann
2021-01-18 7:54 ` Thomas Zimmermann
2021-01-18 9:13 ` Eli Cohen
2021-01-18 9:13 ` Eli Cohen
2021-01-18 9:30 ` Thomas Zimmermann
2021-01-18 9:30 ` Thomas Zimmermann
2021-01-18 9:30 ` Thomas Zimmermann
2021-01-18 10:39 ` Eli Cohen
2021-01-18 10:39 ` Eli Cohen
2021-01-18 13:16 ` Eli Cohen
2021-01-18 13:16 ` Eli Cohen
2021-01-18 13:20 ` Thomas Zimmermann
2021-01-18 13:20 ` Thomas Zimmermann
2021-01-18 13:20 ` Thomas Zimmermann
2021-01-18 13:22 ` Eli Cohen
2021-01-18 13:22 ` Eli Cohen
2021-01-18 13:23 ` Christian König
2021-01-18 13:23 ` Christian König
2021-01-18 13:23 ` Christian König
2021-01-18 14:48 ` Thomas Zimmermann
2021-01-18 14:48 ` Thomas Zimmermann
2021-01-18 14:48 ` Thomas Zimmermann
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=a39c1b62-3e22-2454-d68b-e9eb510891d3@amd.com \
--to=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=elic@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.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.