mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Steven Rostedt <srostedt@redhat.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	Ingo Molnar <mingo@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: TRACE_BRANCH_PROFILING breaks gcc warnings
Date: Wed, 15 Apr 2009 10:12:53 +0200	[thread overview]
Message-ID: <20090415081253.GE18192@elte.hu> (raw)
In-Reply-To: <20090415074659.GA21764@uranus.ravnborg.org>


* Sam Ravnborg <sam@ravnborg.org> wrote:

> > > This has been mentioned before, and I've asked about sending a 
> > > patch that would prevent TRACE_BRANCH_PROFILING from being 
> > > selected with an allyesconfig.
> > > 
> > > It is easy to do. I could make it a selection and not a 
> > > boolean and it will not select it as default, even for 
> > > allyes/modconfig
> 
> We should have a symbol that is only set for allyesconfig builds.
> 
> Then we could do something like:
> 
> config TRACE_BRANCH_PROFILING
> 	depends on !ALLYESCONFIG
> 
> The advantage is that it is obvious why we have defiend it like 
> this rather than some inverse symbols.
> 
> I looked at generating such symbol in kconfig long time ago but 
> never finished it.

ah, nice idea! Should be fairly simple to do, right?

The other option is to disable/remove the branch profiler 
altogether.

	Ingo

      reply	other threads:[~2009-04-15  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14 22:28 Johannes Berg
2009-04-14 22:31 ` Steven Rostedt
2009-04-15  7:37   ` Ingo Molnar
2009-04-15  7:46     ` Sam Ravnborg
2009-04-15  8:12       ` Ingo Molnar [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=20090415081253.GE18192@elte.hu \
    --to=mingo@elte.hu \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sam@ravnborg.org \
    --cc=srostedt@redhat.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

Powered by JetHome