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 1/3] powerpc/powernv: Add config option for removal of memory
Date: Thu, 1 Jun 2017 15:34:38 +1000 [thread overview]
Message-ID: <20170601053440.28976-1-rashmica.g@gmail.com> (raw)
This patch adds the config option to enable the removal
of memory from the kernel mappings at runtime. This needs
to be enabled for the hardware trace macro to work.
Signed-off-by: Rashmica Gupta <rashmica.g@gmail.com>
---
v2 -> v3: Better description
arch/powerpc/platforms/powernv/Kconfig | 8 ++++++++
arch/powerpc/platforms/powernv/Makefile | 1 +
2 files changed, 9 insertions(+)
diff --git a/arch/powerpc/platforms/powernv/Kconfig b/arch/powerpc/platforms/powernv/Kconfig
index 6a6f4ef..92493d6 100644
--- a/arch/powerpc/platforms/powernv/Kconfig
+++ b/arch/powerpc/platforms/powernv/Kconfig
@@ -30,3 +30,11 @@ config OPAL_PRD
help
This enables the opal-prd driver, a facility to run processor
recovery diagnostics on OpenPower machines
+
+config PPC64_HARDWARE_TRACING
+ bool "Enable removal of RAM from kernel mappings for tracing"
+ help
+ Enabling this option allows for the removal of memory (RAM)
+ from the kernel mappings to be used for hardware tracing.
+ depends on MEMORY_HOTREMOVE
+ default n
diff --git a/arch/powerpc/platforms/powernv/Makefile b/arch/powerpc/platforms/powernv/Makefile
index b5d98cb..8fb026d 100644
--- a/arch/powerpc/platforms/powernv/Makefile
+++ b/arch/powerpc/platforms/powernv/Makefile
@@ -12,3 +12,4 @@ obj-$(CONFIG_PPC_SCOM) += opal-xscom.o
obj-$(CONFIG_MEMORY_FAILURE) += opal-memory-errors.o
obj-$(CONFIG_TRACEPOINTS) += opal-tracepoints.o
obj-$(CONFIG_OPAL_PRD) += opal-prd.o
+obj-$(CONFIG_PPC64_HARDWARE_TRACING) += memtrace.o
--
2.9.3
next reply other threads:[~2017-06-01 5:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 5:34 Rashmica Gupta [this message]
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 ` [PATCH v3 3/3] Add documentation for the powerpc memtrace debugfs files Rashmica Gupta
2017-08-31 11:35 ` [v3, " 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-1-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).