Messages in this thread | | | Date | Wed, 23 Dec 2009 16:00:50 -0800 | From | Randy Dunlap <> | Subject | Re: kmemtrace.txt question: kernel parameter(s)? |
| |
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
| |