[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADAEsF-QuUwdOFhjg9aCLZYPhmuNY-CdXQLgv1V1LXUkcJ8ugg@mail.gmail.com>
Date: Tue, 27 Jan 2015 10:07:53 +0800
From: Ganesh Mahendran <opensource.ganesh@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Minchan Kim <minchan@...nel.org>, Nitin Gupta <ngupta@...are.org>,
Linux-MM <linux-mm@...ck.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] mm/zsmalloc: add log for module load/unload
Hello, Andrew
2015-01-27 7:19 GMT+08:00 Andrew Morton <akpm@...ux-foundation.org>:
> On Sat, 24 Jan 2015 21:48:41 +0800 Ganesh Mahendran <opensource.ganesh@...il.com> wrote:
>
>> Sometimes, we want to know whether a module is loaded or unloaded
>> from the log.
>
> Why? What's special about zsmalloc?
>
> Please provide much better justification than this.
When I debug with the zsmalloc module built in kernel.
After system boots up, I did not see:
/sys/kernel/debug/zsmalloc dir.
Although the reason for this is that I made a mistake. I
forgot to add debugfs entry in /etc/fstab.
But I think it is suitable to add information for a module load/unload.
Then we can get this by:
dmesg | grep zsmalloc.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists