mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julian Braha <julianbraha@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib: fix kconfig dependency on ARCH_WANT_FRAME_POINTERS
Date: Wed, 24 Mar 2021 20:09:06 -0400	[thread overview]
Message-ID: <2598523.FcGXNBlX6l@ubuntu-mate-laptop> (raw)
In-Reply-To: <CAMuHMdU+27du_WVSzWQF3O7Y2E2TDHRfpYzspH2XQXhgd+XZJA@mail.gmail.com>

On Wednesday, March 24, 2021 4:12:34 AM EDT you wrote:
> Hi Julian,
> 
> On Wed, Mar 24, 2021 at 7:48 AM Julian Braha <julianbraha@gmail.com> wrote:
> > On Monday, March 22, 2021 3:43:41 AM EDT you wrote:
> > > On Sun, Mar 21, 2021 at 11:40 PM Julian Braha <julianbraha@gmail.com> wrote:
> > > > On Sunday, March 21, 2021 2:28:43 PM EDT you wrote:
> > > > > On Sat, Mar 20, 2021 at 1:17 AM Julian Braha <julianbraha@gmail.com> wrote:
> > > > > > When LATENCYTOP is enabled and ARCH_WANT_FRAME_POINTERS
> > > > > > is disabled, Kbuild gives the following warning:
> > > > > >
> > > > > > WARNING: unmet direct dependencies detected for FRAME_POINTER
> > > > > >   Depends on [n]: DEBUG_KERNEL [=y] && (M68K || UML || SUPERH) || ARCH_WANT_FRAME_POINTERS [=n] || MCOUNT [=n]
> > > > > >   Selected by [y]:
> > > > > >   - LATENCYTOP [=y] && DEBUG_KERNEL [=y] && STACKTRACE_SUPPORT [=y] && PROC_FS [=y] && !MIPS && !PPC && !S390 && !MICROBLAZE && !ARM && !ARC && !X86
> > > > > >
> > > > > > This is because LATENCYTOP selects FRAME_POINTER,
> > > > > > without selecting or depending on ARCH_WANT_FRAME_POINTERS,
> > > > > > despite FRAME_POINTER depending on ARCH_WANT_FRAME_POINTERS.
> > > > > >
> > > > > > Signed-off-by: Julian Braha <julianbraha@gmail.com>
> > > > >
> > > > > Thanks for your patch!
> > > > >
> > > > > > --- a/lib/Kconfig.debug
> > > > > > +++ b/lib/Kconfig.debug
> > > > > > @@ -1675,6 +1675,7 @@ config LATENCYTOP
> > > > > >         depends on DEBUG_KERNEL
> > > > > >         depends on STACKTRACE_SUPPORT
> > > > > >         depends on PROC_FS
> > > > > > +       select ARCH_WANT_FRAME_POINTERS if !MIPS && !PPC && !S390 && !MICROBLAZE && !ARM && !ARC && !X86
> > > > >
> > > > > ARCH_WANT_FRAME_POINTERS is a symbol that is only to be selected by
> > > > > architecture-specific configuration, and must not be overridden:
> > > > >
> > > > >     # Select this config option from the architecture Kconfig, if it
> > > > >     # is preferred to always offer frame pointers as a config
> > > > >     # option on the architecture (regardless of KERNEL_DEBUG):
> > > > >
> > > > > Probably this should be turned into a depends instead?
> > > > >
> > > > > >         select FRAME_POINTER if !MIPS && !PPC && !S390 && !MICROBLAZE && !ARM && !ARC && !X86
> > > > > >         select KALLSYMS
> > > > > >         select KALLSYMS_ALL
> > >
> > > > Making this a 'depends' causes a recursive dependency error.
> > > > Any other ideas?
> > >
> > > What about
> > >
> > >     -select FRAME_POINTER if !MIPS && !PPC && !S390 && !MICROBLAZE &&
> > > !ARM && !ARC && !X86
> > >     +depends on FRAME_POINTER if !MIPS && !PPC && !S390 && !MICROBLAZE
> > > && !ARM && !ARC && !X86
> > >
> > > ?
> >
> > Sadly, this won't work either. In Kconfig, 'depends' cannot have an 'if' after it (only 'select' can.)
> > Kbuild gives an error for this.
> 
> Oops
> 
>     select FRAME_POINTER || MIPS || PPC || S390 || MICROBLAZE || ARM
> || ARC || X86
> 
> of course.
> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 
> 

Hi Geert,

I think it's a typo, but if you meant:
select FRAME_POINTER if MIPS || PPC || S390 || MICROBLAZE || ARM || ARC || X86
Then that works.

- Julian Braha




  reply	other threads:[~2021-03-25  0:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20  0:15 Julian Braha
2021-03-21 18:28 ` Geert Uytterhoeven
2021-03-21 22:40   ` Julian Braha
2021-03-22  7:43     ` Geert Uytterhoeven
2021-03-24  6:48       ` Julian Braha
2021-03-24  8:12         ` Geert Uytterhoeven
2021-03-25  0:09           ` Julian Braha [this message]
2021-03-25  7:20             ` Geert Uytterhoeven
2021-03-26 17:32               ` Julian Braha

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=2598523.FcGXNBlX6l@ubuntu-mate-laptop \
    --to=julianbraha@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®