From: Rashmica Gupta <rashmica.g@gmail.com>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, mpe@ellerman.id.au,
anton@samba.org, npiggin@gmail.com, bsingharora@gmail.com,
oohall@gmail.com
Subject: Re: [PATCH 1/2] powerpc/powernv: Add config option for removal of memory
Date: Wed, 3 May 2017 13:52:27 +1000 [thread overview]
Message-ID: <7d3de1f8-a23c-67e9-46e4-6b6677682010@gmail.com> (raw)
In-Reply-To: <9618346f-36ef-2943-f5c0-5be1e87b28f9@linux.vnet.ibm.com>
On 28/04/17 19:39, Anshuman Khandual wrote:
> On 04/28/2017 11:12 AM, Rashmica Gupta wrote:
>> Signed-off-by: Rashmica Gupta <rashmica.g@gmail.com>
> Please describe a bit about the function/feature you are trying
> to add with this new config option. The subject says " Add config
> option for removal of memory" but I guess its not related to
> memory hotplug but about hardware enabled tracing IIUC.
Correct!
> Hence
> it should have some amount of description.
>
>> ---
>> arch/powerpc/platforms/powernv/Kconfig | 4 ++++
>> arch/powerpc/platforms/powernv/Makefile | 1 +
>> 2 files changed, 5 insertions(+)
>>
>> diff --git a/arch/powerpc/platforms/powernv/Kconfig b/arch/powerpc/platforms/powernv/Kconfig
>> index 6a6f4ef..1b8b3a8 100644
>> --- a/arch/powerpc/platforms/powernv/Kconfig
>> +++ b/arch/powerpc/platforms/powernv/Kconfig
>> @@ -30,3 +30,7 @@ config OPAL_PRD
>> help
>> This enables the opal-prd driver, a facility to run processor
>> recovery diagnostics on OpenPower machines
>> +
>> +config HARDWARE_TRACING
> This is too generic for platform specific feature and also it does
> not intend to fit into a generic HW tracing infrastructure. IMHO
> it should be named something like "PPC64_HARDWARE_TRACING" or
> something similar.
>
>> + bool 'Enable removal of memory for hardware memory tracing'
> If this memory is going to be taken out of memblock like normal
> memory hotplug and eventually goes away from kernel control, then
> you need to be more specific about its usage.
>
All good points! Thanks for the review.
prev parent reply other threads:[~2017-05-03 3:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 5:42 [PATCH 1/2] powerpc/powernv: Add config option for removal of memory Rashmica Gupta
2017-04-28 5:42 ` [PATCH 2/2] v1 powerpc/powernv: Enable removal of memory for in memory tracing Rashmica Gupta
2017-04-28 9:52 ` Anshuman Khandual
2017-05-03 3:52 ` Rashmica Gupta
2017-05-03 6:08 ` Rashmica Gupta
2017-05-03 11:25 ` Anshuman Khandual
2017-05-03 6:08 ` Rashmica Gupta
2017-05-03 11:56 ` Anshuman Khandual
2017-05-09 7:06 ` Rashmica Gupta
2017-05-14 4:55 ` Anshuman Khandual
2017-05-15 3:34 ` Rashmica Gupta
2017-05-15 4:35 ` Anshuman Khandual
2017-04-28 9:39 ` [PATCH 1/2] powerpc/powernv: Add config option for removal of memory Anshuman Khandual
2017-05-03 3:52 ` Rashmica Gupta [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=7d3de1f8-a23c-67e9-46e4-6b6677682010@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).