linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Minchan Kim <minchan@kernel.org>
To: Ganesh Mahendran <opensource.ganesh@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Nitin Gupta <ngupta@vflare.org>, Linux-MM <linux-mm@kvack.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm/zsmalloc: add log for module load/unload
Date: Tue, 27 Jan 2015 12:23:07 +0900	[thread overview]
Message-ID: <20150127032307.GB16797@blaptop> (raw)
In-Reply-To: <CADAEsF-QuUwdOFhjg9aCLZYPhmuNY-CdXQLgv1V1LXUkcJ8ugg@mail.gmail.com>

Hello Ganesh,

On Tue, Jan 27, 2015 at 10:07:53AM +0800, Ganesh Mahendran wrote:
> Hello, Andrew
> 
> 2015-01-27 7:19 GMT+08:00 Andrew Morton <akpm@linux-foundation.org>:
> > On Sat, 24 Jan 2015 21:48:41 +0800 Ganesh Mahendran <opensource.ganesh@gmail.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.

I understand your trouble but it's general problem, not zsmalloc specific.
Then, if you really want to fix, you should approach more generic ways.

Thanks.

-- 
Kind regards,
Minchan Kim

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2015-01-27  3:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-24 13:48 [PATCH] mm/zsmalloc: add log for module load/unload Ganesh Mahendran
2015-01-26 23:19 ` Andrew Morton
2015-01-27  2:07   ` Ganesh Mahendran
2015-01-27  3:23     ` Minchan Kim [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=20150127032307.GB16797@blaptop \
    --to=minchan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ngupta@vflare.org \
    --cc=opensource.ganesh@gmail.com \
    /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).