From: Randy Dunlap <randy.dunlap@oracle.com>
To: Li Zefan <lizf@cn.fujitsu.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
eduard.munteanu@linux360.ro,
Pekka Enberg <penberg@cs.helsinki.fi>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: kmemtrace.txt question: kernel parameter(s)?
Date: Wed, 23 Dec 2009 16:00:50 -0800 [thread overview]
Message-ID: <20091223160050.0c282ad2.randy.dunlap@oracle.com> (raw)
In-Reply-To: <4B2AD38D.3070605@cn.fujitsu.com>
On Fri, 18 Dec 2009 08:57:49 +0800 Li Zefan wrote:
> Randy Dunlap wrote:
> > Hi,
> >
> > Documentation/trace/kmemtrace.txt says:
> >
> > Q: 'cat /sys/kernel/debug/kmemtrace/total_overruns' is non-zero, how do I fix
> > this? Should I worry?
> > A: If it's non-zero, this affects kmemtrace's accuracy, depending on how
> > large the number is. You can fix it by supplying a higher
> > 'kmemtrace.subbufs=N' kernel parameter.
> >
> >
> > Where is this kernel parameter implemented and where is it documented?
> > or should this Answer just be fixed?
> >
>
> The whole documentation is out-dated. The original kmemtrace was based on
> relay, and then it moved to ftrace, without updating the documentation.
Thank you. I guess that explains why kmemtraced (from kmemtrace-user.git)
fails with:
Could not open() file /sys/kernel/debug/kmemtrace/cpu0: No such file or directory
Eduard, can we get Documentation/trace/kmemtrace.txt updated, please?
---
~Randy
next prev parent reply other threads:[~2009-12-24 0:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 22:13 Randy Dunlap
2009-12-18 0:57 ` Li Zefan
2009-12-24 0:00 ` Randy Dunlap [this message]
2010-03-27 4:27 ` Randy Dunlap
2010-03-28 8:26 ` [PATCH] Remove Documentation/trace/kmemtrace.txt Eduard - Gabriel Munteanu
2010-03-28 8:33 ` Pekka Enberg
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=20091223160050.0c282ad2.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
/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
Powered by JetHome