public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Dave Airlie <airlied@gmail.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: ftrace scripts and make V=1
Date: Wed, 5 Aug 2009 10:18:24 +0200	[thread overview]
Message-ID: <20090805081824.GA1810@elte.hu> (raw)
In-Reply-To: <20090805080858.GA2947@merkur.ravnborg.org>


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

> On Wed, Aug 05, 2009 at 05:23:26PM +1000, Dave Airlie wrote:
> > Hey,
> > 
> > So I spent 3-4 hrs today (I'm stupid yes) tracking down a .o breakage by
> > blaming rawhide gcc/binutils as I was using make V=1and seeing only the
> > compiler chain running,
> > 
> > However some ftrace script was sneaking in afterwards
> > and screwing up the .o without mentioning itself.
> > 
> > Surely V=1 should print all these shitty scripts its running?
> 
> The problem is that V=1 is already too chatty,
> so people sometimes hide their stuff - as in this case.
> 
> I have for some time thought about adding some option
> so we can select between:
>  - less chatty than today - but print the usefull stuff
>  - full debug - print almost everything
> 
> It is not that this is hard to implment.
> But I never have made up my mind how to enable this.
> 
> V=1 - could be the "less chatty" mode
> V=2 - could be the "full debug mode"
> 
> But we already use "V=2" to tell what caused a file to be rebuild.
> This is on the other hand very seldomly used so we could get
> away with a new way to request this.
> So we limit V=n to select between different verbosity levels.
> 
> What do you think?

definitely sounds useful ...

	Ingo

  reply	other threads:[~2009-08-05  8:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05  7:23 ftrace scripts and make V=1 Dave Airlie
2009-08-05  7:29 ` Ingo Molnar
2009-08-06  2:00   ` Steven Rostedt
2009-08-06  3:43     ` Ingo Molnar
2009-08-06 15:02       ` Steven Rostedt
2009-08-06 12:25     ` [tip:tracing/urgent] tracing: do not use functions starting with .L in recordmcount.pl tip-bot for Steven Rostedt
2009-08-06 12:34       ` Ingo Molnar
2009-08-05  8:08 ` ftrace scripts and make V=1 Sam Ravnborg
2009-08-05  8:18   ` Ingo Molnar [this message]
2009-08-05  8:52 ` Andi Kleen

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=20090805081824.GA1810@elte.hu \
    --to=mingo@elte.hu \
    --cc=airlied@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=torvalds@linux-foundation.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