From: Rashmica Gupta <rashmica.g@gmail.com>
To: linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au,
anton@samba.org, npiggin@gmail.com, bsingharora@gmail.com,
oohall@gmail.com, khandual@linux.vnet.ibm.com
Cc: Rashmica Gupta <rashmica.g@gmail.com>
Subject: [PATCH v3 3/3] Add documentation for the powerpc memtrace debugfs files
Date: Thu, 1 Jun 2017 15:34:40 +1000 [thread overview]
Message-ID: <20170601053440.28976-3-rashmica.g@gmail.com> (raw)
In-Reply-To: <20170601053440.28976-1-rashmica.g@gmail.com>
CONFIG_PPC64_HARDWARE_TRACING must be set to use this feature. This can only
be used on powernv platforms.
Signed-off-by: Rashmica Gupta <rashmica.g@gmail.com>
---
Documentation/ABI/testing/ppc-memtrace | 45 ++++++++++++++++++++++++++++++++++
1 file changed, 45 insertions(+)
create mode 100644 Documentation/ABI/testing/ppc-memtrace
diff --git a/Documentation/ABI/testing/ppc-memtrace b/Documentation/ABI/testing/ppc-memtrace
new file mode 100644
index 0000000..f7eff02
--- /dev/null
+++ b/Documentation/ABI/testing/ppc-memtrace
@@ -0,0 +1,45 @@
+What: /sys/kernel/debug/powerpc/memtrace
+Date: May 2017
+KernelVersion: 4.13?
+Contact: linuxppc-dev@lists.ozlabs.org
+Description: This folder contains the relevant debugfs files for the
+ hardware trace macro to use. CONFIG_PPC64_HARDWARE_TRACING
+ must be set.
+
+What: /sys/kernel/debug/powerpc/memtrace/enable
+Date: May 2017
+KernelVersion: 4.13?
+Contact: linuxppc-dev@lists.ozlabs.org
+Description: Write an integer containing the size of the memory you want
+ removed from each NUMA node to this file - it must be
+ aligned to the memblock size. This amount of RAM will be
+ removed from the kernel mappings and the following debugfs
+ files will be created. This can only be successfully done
+ once per boot. Once memory is successfully removed from
+ each node, the following files are created.
+
+What: /sys/kernel/debug/powerpc/memtrace/<node-id>
+Date: May 2017
+KernelVersion: 4.13?
+Contact: linuxppc-dev@lists.ozlabs.org
+Description: This directory contains information about the removed memory
+ from the specific NUMA node.
+
+What: /sys/kernel/debug/powerpc/memtrace/<node-id>/size
+Date: May 2017
+KernelVersion: 4.13?
+Contact: linuxppc-dev@lists.ozlabs.org
+Description: This contains the size of the memory removed from the node.
+
+What: /sys/kernel/debug/powerpc/memtrace/<node-id>/start
+Date: May 2017
+KernelVersion: 4.13?
+Contact: linuxppc-dev@lists.ozlabs.org
+Description: This contains the start address of the removed memory.
+
+What: /sys/kernel/debug/powerpc/memtrace/<node-id>/trace
+Date: May 2017
+KernelVersion: 4.13?
+Contact: linuxppc-dev@lists.ozlabs.org
+Description: This is where the hardware trace macro will output the trace
+ it generates.
--
2.9.3
next prev parent reply other threads:[~2017-06-01 5:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 5:34 [PATCH v3 1/3] powerpc/powernv: Add config option for removal of memory Rashmica Gupta
2017-06-01 5:34 ` [PATCH v3 2/3] powerpc/powernv: Enable removal of memory for in memory tracing Rashmica Gupta
2017-08-31 11:35 ` [v3, " Michael Ellerman
2017-06-01 5:34 ` Rashmica Gupta [this message]
2017-08-31 11:35 ` [v3, 3/3] Add documentation for the powerpc memtrace debugfs files Michael Ellerman
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=20170601053440.28976-3-rashmica.g@gmail.com \
--to=rashmica.g@gmail.com \
--cc=anton@samba.org \
--cc=bsingharora@gmail.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=oohall@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).