linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>, Randy Dunlap <rdunlap@xenotime.net>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	Oleg Nesterov <oleg@redhat.com>, Mark Wielaard <mjw@redhat.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Naren A Devaiah <naren.devaiah@in.ibm.com>,
	Jim Keniston <jkenisto@linux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	"Frank Ch. Eigler" <fche@redhat.com>,
	Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCHv9 2.6.35-rc4-tip 10/13]  perf: Re-Add make_absolute_path
Date: Wed, 14 Jul 2010 13:23:32 -0300	[thread overview]
Message-ID: <20100714162332.GA4000@ghostprotocols.net> (raw)
In-Reply-To: <1279075767.4190.1.camel@localhost>

Em Tue, Jul 13, 2010 at 10:49:27PM -0400, Steven Rostedt escreveu:
> On Mon, 2010-07-12 at 13:12 -0300, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Jul 12, 2010 at 10:30:36AM -0400, Steven Rostedt escreveu:

> > Well, I prefer to follow the kernel way of doing things, i.e. to
> > propagate as much as possible up the callchain the error return value,
> > so that the apps can handle it in any way they prefer, i.e. die() calls
> > in tools/perf/builtin-foo.c are okayish, but not on tools/perf/util/.

> Ah, yes, die is a bit strong. And I have been starting to avoid them
> too. Although, when malloc fails, it's almost certain that the app will
> die soon anyway ;-)

The interesting thing is that years ago, when modules were being
introduced in the kernel and panic() calls for things like out of memory
conditions were being removed, some people made the same comments, 'if
that happens, you're doomed anyway!' :-)

I can see things like trying to load a huge perf.data file in the TUI
interface failing and the user just being warned about it and going on
with life loading some other file, etc.

Certainly it is interesting to try to apply as much as possible of the
mindset (and fear of criticism) present when coding for the kernel when
one codes for userland.

- Arnaldo

  reply	other threads:[~2010-07-14 16:24 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-12 10:32 [PATCHv9 2.6.35-rc4-tip 0/13] Uprobes Patches: Srikar Dronamraju
2010-07-12 10:32 ` [PATCHv9 2.6.35-rc4-tip 1/13] mm: Move replace_page() / write_protect_page() to mm/memory.c Srikar Dronamraju
2010-07-12 10:32 ` [PATCHv9 2.6.35-rc4-tip 2/13] uprobes: Breakpoint insertion/removal in user space applications Srikar Dronamraju
2010-07-20  4:28   ` Christoph Hellwig
2010-07-20  7:22     ` Srikar Dronamraju
2010-08-04 12:05       ` Peter Zijlstra
2010-08-04 12:48         ` Srikar Dronamraju
2010-08-04 13:02           ` Peter Zijlstra
2010-07-12 10:32 ` [PATCHv9 2.6.35-rc4-tip 3/13] uprobes: Slot allocation for Execution out of line(XOL) Srikar Dronamraju
2010-07-12 10:32 ` [PATCHv9 2.6.35-rc4-tip 4/13] uprobes: x86 specific functions for user space breakpointing Srikar Dronamraju
2010-07-12 10:33 ` [PATCHv9 2.6.35-rc4-tip 5/13] uprobes: Uprobes (un)registration and exception handling Srikar Dronamraju
2010-07-12 10:33 ` [PATCHv9 2.6.35-rc4-tip 6/13] uprobes: X86 support for Uprobes Srikar Dronamraju
2010-07-12 10:33 ` [PATCHv9 2.6.35-rc4-tip 7/13] uprobes: Uprobes Documentation Srikar Dronamraju
2010-07-12 10:33 ` [PATCHv9 2.6.35-rc4-tip 8/13] trace: Extract out common code for kprobes/uprobes traceevents Srikar Dronamraju
2010-07-12 10:34 ` [PATCHv9 2.6.35-rc4-tip 9/13] trace: uprobes trace_event interface Srikar Dronamraju
2010-07-12 10:34 ` [PATCHv9 2.6.35-rc4-tip 10/13] perf: Re-Add make_absolute_path Srikar Dronamraju
2010-07-12 14:00   ` Arnaldo Carvalho de Melo
2010-07-12 14:30     ` Steven Rostedt
2010-07-12 16:12       ` Arnaldo Carvalho de Melo
2010-07-14  2:49         ` Steven Rostedt
2010-07-14 16:23           ` Arnaldo Carvalho de Melo [this message]
2010-07-14 20:45             ` Ingo Molnar
2010-07-14 20:50               ` Mathieu Desnoyers
2010-07-12 15:33     ` Srikar Dronamraju
2010-07-12 16:26       ` Arnaldo Carvalho de Melo
2010-07-12 17:26         ` Srikar Dronamraju
2010-07-12 10:34 ` [PATCHv9 2.6.35-rc4-tip 11/13] perf: perf interface for uprobes Srikar Dronamraju
2010-07-12 16:03   ` Arnaldo Carvalho de Melo
2010-07-12 17:32     ` Srikar Dronamraju
2010-07-12 10:34 ` [PATCHv9 2.6.35-rc4-tip 12/13] [RFC] perf: Show Potential probe points Srikar Dronamraju
2010-07-12 14:41   ` Arnaldo Carvalho de Melo
2010-07-12 15:55     ` Srikar Dronamraju
2010-07-12 10:34 ` [PATCHv9 2.6.35-rc4-tip 13/13] [RFC] perf: show functions in a file without using pid Srikar Dronamraju
2010-07-20  4:19 ` [PATCHv9 2.6.35-rc4-tip 0/13] Uprobes Patches: Christoph Hellwig
2010-07-20  6:38   ` Srikar Dronamraju
2010-07-20 21:03     ` Arnaldo Carvalho de Melo
2010-07-21  2:42       ` Srikar Dronamraju
2010-07-21 13:08         ` Steven Rostedt
2010-07-21 13:21           ` Srikar Dronamraju
2010-07-21 13:26             ` Christoph Hellwig
2010-07-21 14:10               ` Steven Rostedt
2010-07-21 14:22         ` Arnaldo Carvalho de Melo
2010-07-21 15:50           ` Steven Rostedt
2010-07-21 13:19       ` Srikar Dronamraju

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=20100714162332.GA4000@ghostprotocols.net \
    --to=acme@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=ananth@in.ibm.com \
    --cc=fche@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=hch@infradead.org \
    --cc=jkenisto@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@elte.hu \
    --cc=mjw@redhat.com \
    --cc=naren.devaiah@in.ibm.com \
    --cc=oleg@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rdunlap@xenotime.net \
    --cc=rostedt@goodmis.org \
    --cc=srikar@linux.vnet.ibm.com \
    --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;
as well as URLs for NNTP newsgroup(s).