linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	mpe@ellerman.id.au, npiggin@gmail.com,
	christophe.leroy@csgroup.eu, paulus@ozlabs.org
Cc: naveen@kernel.org, linuxppc-dev@lists.ozlabs.org,
	kernel test robot <lkp@intel.com>
Subject: Re: [RFC PATCH] powerpc: Add check to select PPC_RADIX_BROADCAST_TLBIE
Date: Tue, 08 Apr 2025 14:31:40 +0530	[thread overview]
Message-ID: <871pu3kowb.fsf@gmail.com> (raw)
In-Reply-To: <0ed6cb24-e8dc-4821-91a9-b638ca862878@csgroup.eu>

Christophe Leroy <christophe.leroy@csgroup.eu> writes:

> Le 07/04/2025 à 21:10, Ritesh Harjani (IBM) a écrit :
>> Madhavan Srinivasan <maddy@linux.ibm.com> writes:
>> 
>>> Commit 3d45a3d0d2e6 ("powerpc: Define config option for processors with broadcast TLBIE")
>> 
>> We may need to add above to Fixes tag as well, no?
>> 
>>> added a config option PPC_RADIX_BROADCAST_TLBIE to support processors with
>>> broadcast TLBIE. Since this option is relevant only for RADIX_MMU, add
>>> a check as a dependency to enable PPC_RADIX_BROADCAST_TLBIE in both
>>> powernv and pseries configs. This fixes the unmet config dependency
>>> warning reported
>>>
>>>     WARNING: unmet direct dependencies detected for PPC_RADIX_BROADCAST_TLBIE
>>>       Depends on [n]: PPC_RADIX_MMU [=n]
>>>       Selected by [y]:
>>>       - PPC_PSERIES [=y] && PPC64 [=y] && PPC_BOOK3S [=y]
>>>
>>> Reported-by: kernel test robot <lkp@intel.com>
>>> Closes: https://lore.kernel.org/oe-kbuild-all/202504051857.jRqxM60c-lkp@intel.com/
>>> Signed-off-by: Madhavan Srinivasan <maddy@linux.ibm.com>
>> 
>> It's a bit strange that even though PPC_RADIX_BROADCAST_TLBIE adds
>> PPC_RADIX_MMU as a dependency where is it defined, we still have to add
>> an extra check for the same dependency to enable this for any platform.
>
> That's expected, see 

Yes. I had figured that out. 

> https://docs.kernel.org/kbuild/kconfig-language.html#menu-attributes :

Ok! Good to see we have this properly documented as well. Thanks for
pointing out the documentation link.

>
> select should be used with care. select will force a symbol to a value 
> without visiting the dependencies. By abusing select you are able to 
> select a symbol FOO even if FOO depends on BAR that is not set. In 
> general use select only for non-visible symbols (no prompts anywhere) 
> and for symbols with no dependencies. That will limit the usefulness but 
> on the other hand avoid the illegal configurations all over.
>
> Christophe
>

Make sense. Thanks! for adding the details.

-ritesh


  reply	other threads:[~2025-04-08  9:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07  8:40 [RFC PATCH] powerpc: Add check to select PPC_RADIX_BROADCAST_TLBIE Madhavan Srinivasan
2025-04-07 17:03 ` Venkat Rao Bagalkote
2025-04-07 19:10 ` Ritesh Harjani (IBM)
2025-04-08  6:02   ` Christophe Leroy
2025-04-08  9:01     ` Ritesh Harjani [this message]
2025-04-21  9:41 ` Madhavan Srinivasan

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=871pu3kowb.fsf@gmail.com \
    --to=ritesh.list@gmail.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=lkp@intel.com \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=naveen@kernel.org \
    --cc=npiggin@gmail.com \
    --cc=paulus@ozlabs.org \
    /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).