All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cody P Schafer <cody@linux.vnet.ibm.com>
To: Michael Neuling <mikey@neuling.org>
Cc: Deepthi Dharwar <deepthi@linux.vnet.ibm.com>,
	Paul Bolle <pebolle@tiscali.nl>,
	Gavin Shan <shangw@linux.vnet.ibm.com>,
	Li Zhong <zhong@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
	"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/pseries: relocate "config DTL" so KConfig nests properly
Date: Tue, 13 May 2014 00:12:37 -0700	[thread overview]
Message-ID: <5371C5E5.6070701@linux.vnet.ibm.com> (raw)
In-Reply-To: <1399962216.7554.63.camel@ale.ozlabs.ibm.com>

On 05/12/2014 11:23 PM, Michael Neuling wrote:
>> powerpc/pseries: relocate "config DTL" so KConfig nests properly
>
> I don't know what that means.  Can you describe it in more detail?
>

So the "config DTL" refers to the configuration entry.

The "nests properly" refers to the indent that 'make menuconfig' shows 
when a config-option that depends on the config-option proceeding it.

In this case, moving config DTL up so it is below config PPC_SPLPAR 
means that menuconfig will show config DTL nicely indented right below 
config PPC_SPLPAR when PPC_SPLPAR is enabled.

To contrast that, right now if I enable PPC_SPLPAR in menuconfig, all I 
can immediately tell is that "something showed up further down the list 
where I wasn't looking", and I end up having to toggle the option a few 
times to figure out what showed up, or look at the KConfig to find out 
that config DTL depends on config PPC_SPLPAR.

Essentially, this enables menuconfig to provide a visual hint about the 
dependencies between options.

> Mikey
>
>
> On Mon, 2014-05-12 at 20:09 -0700, Cody P Schafer wrote:
>> Signed-off-by: Cody P Schafer <cody@linux.vnet.ibm.com>
>> ---
>>   arch/powerpc/platforms/pseries/Kconfig | 20 ++++++++++----------
>>   1 file changed, 10 insertions(+), 10 deletions(-)
>>
>> diff --git a/arch/powerpc/platforms/pseries/Kconfig b/arch/powerpc/platforms/pseries/Kconfig
>> index 2cb8b77..e00dd4d 100644
>> --- a/arch/powerpc/platforms/pseries/Kconfig
>> +++ b/arch/powerpc/platforms/pseries/Kconfig
>> @@ -33,6 +33,16 @@ config PPC_SPLPAR
>>   	  processors, that is, which share physical processors between
>>   	  two or more partitions.
>>
>> +config DTL
>> +	bool "Dispatch Trace Log"
>> +	depends on PPC_SPLPAR && DEBUG_FS
>> +	help
>> +	  SPLPAR machines can log hypervisor preempt & dispatch events to a
>> +	  kernel buffer. Saying Y here will enable logging these events,
>> +	  which are accessible through a debugfs file.
>> +
>> +	  Say N if you are unsure.
>> +
>>   config PSERIES_MSI
>>          bool
>>          depends on PCI_MSI && PPC_PSERIES && EEH
>> @@ -122,13 +132,3 @@ config HV_PERF_CTRS
>>   	  systems. 24x7 is available on Power 8 systems.
>>
>>             If unsure, select Y.
>> -
>> -config DTL
>> -	bool "Dispatch Trace Log"
>> -	depends on PPC_SPLPAR && DEBUG_FS
>> -	help
>> -	  SPLPAR machines can log hypervisor preempt & dispatch events to a
>> -	  kernel buffer. Saying Y here will enable logging these events,
>> -	  which are accessible through a debugfs file.
>> -
>> -	  Say N if you are unsure.
>

WARNING: multiple messages have this Message-ID (diff)
From: Cody P Schafer <cody@linux.vnet.ibm.com>
To: Michael Neuling <mikey@neuling.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Deepthi Dharwar <deepthi@linux.vnet.ibm.com>,
	Gavin Shan <shangw@linux.vnet.ibm.com>,
	Li Zhong <zhong@linux.vnet.ibm.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Paul Bolle <pebolle@tiscali.nl>,
	"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
	Paul Mackerras <paulus@samba.org>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/pseries: relocate "config DTL" so KConfig nests properly
Date: Tue, 13 May 2014 00:12:37 -0700	[thread overview]
Message-ID: <5371C5E5.6070701@linux.vnet.ibm.com> (raw)
In-Reply-To: <1399962216.7554.63.camel@ale.ozlabs.ibm.com>

On 05/12/2014 11:23 PM, Michael Neuling wrote:
>> powerpc/pseries: relocate "config DTL" so KConfig nests properly
>
> I don't know what that means.  Can you describe it in more detail?
>

So the "config DTL" refers to the configuration entry.

The "nests properly" refers to the indent that 'make menuconfig' shows 
when a config-option that depends on the config-option proceeding it.

In this case, moving config DTL up so it is below config PPC_SPLPAR 
means that menuconfig will show config DTL nicely indented right below 
config PPC_SPLPAR when PPC_SPLPAR is enabled.

To contrast that, right now if I enable PPC_SPLPAR in menuconfig, all I 
can immediately tell is that "something showed up further down the list 
where I wasn't looking", and I end up having to toggle the option a few 
times to figure out what showed up, or look at the KConfig to find out 
that config DTL depends on config PPC_SPLPAR.

Essentially, this enables menuconfig to provide a visual hint about the 
dependencies between options.

> Mikey
>
>
> On Mon, 2014-05-12 at 20:09 -0700, Cody P Schafer wrote:
>> Signed-off-by: Cody P Schafer <cody@linux.vnet.ibm.com>
>> ---
>>   arch/powerpc/platforms/pseries/Kconfig | 20 ++++++++++----------
>>   1 file changed, 10 insertions(+), 10 deletions(-)
>>
>> diff --git a/arch/powerpc/platforms/pseries/Kconfig b/arch/powerpc/platforms/pseries/Kconfig
>> index 2cb8b77..e00dd4d 100644
>> --- a/arch/powerpc/platforms/pseries/Kconfig
>> +++ b/arch/powerpc/platforms/pseries/Kconfig
>> @@ -33,6 +33,16 @@ config PPC_SPLPAR
>>   	  processors, that is, which share physical processors between
>>   	  two or more partitions.
>>
>> +config DTL
>> +	bool "Dispatch Trace Log"
>> +	depends on PPC_SPLPAR && DEBUG_FS
>> +	help
>> +	  SPLPAR machines can log hypervisor preempt & dispatch events to a
>> +	  kernel buffer. Saying Y here will enable logging these events,
>> +	  which are accessible through a debugfs file.
>> +
>> +	  Say N if you are unsure.
>> +
>>   config PSERIES_MSI
>>          bool
>>          depends on PCI_MSI && PPC_PSERIES && EEH
>> @@ -122,13 +132,3 @@ config HV_PERF_CTRS
>>   	  systems. 24x7 is available on Power 8 systems.
>>
>>             If unsure, select Y.
>> -
>> -config DTL
>> -	bool "Dispatch Trace Log"
>> -	depends on PPC_SPLPAR && DEBUG_FS
>> -	help
>> -	  SPLPAR machines can log hypervisor preempt & dispatch events to a
>> -	  kernel buffer. Saying Y here will enable logging these events,
>> -	  which are accessible through a debugfs file.
>> -
>> -	  Say N if you are unsure.
>


  reply	other threads:[~2014-05-13  7:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13  3:09 [PATCH] powerpc/pseries: relocate "config DTL" so KConfig nests properly Cody P Schafer
2014-05-13  3:09 ` Cody P Schafer
2014-05-13  6:23 ` Michael Neuling
2014-05-13  6:23   ` Michael Neuling
2014-05-13  7:12   ` Cody P Schafer [this message]
2014-05-13  7:12     ` Cody P Schafer
2014-05-13 23:04     ` Michael Neuling
2014-05-13 23:04       ` Michael Neuling

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=5371C5E5.6070701@linux.vnet.ibm.com \
    --to=cody@linux.vnet.ibm.com \
    --cc=deepthi@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=paulus@samba.org \
    --cc=pebolle@tiscali.nl \
    --cc=shangw@linux.vnet.ibm.com \
    --cc=srivatsa.bhat@linux.vnet.ibm.com \
    --cc=zhong@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.