public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Andi Kleen <andi@firstfloor.org>
Cc: Stephane Eranian <eranian@google.com>,
	Lin Ming <ming.m.lin@intel.com>, Ingo Molnar <mingo@elte.hu>,
	lkml <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: [RFC PATCH 3/3 v2] perf: Update perf tool to monitor uncore events
Date: Sun, 21 Nov 2010 19:30:38 +0100	[thread overview]
Message-ID: <1290364238.2153.89.camel@laptop> (raw)
In-Reply-To: <20101121182810.GA16299@basil.fritz.box>

On Sun, 2010-11-21 at 19:28 +0100, Andi Kleen wrote:
> > I would argue against restricting the tool, print a warning perhaps. I
> > mean, give the user all the rope he needs and tell him how to tie the
> > knot is the unix way, right? :-)
> 
> WARNING: the following information is completely useless and wrong
> 
> Basically reporting rip here is lying and don't think lying is the
> "Unix way".

Yeah, unless there's only one task running on that socket.. Dude,
really, lighten up.

  reply	other threads:[~2010-11-21 18:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-21 12:01 [RFC PATCH 3/3 v2] perf: Update perf tool to monitor uncore events Lin Ming
2010-11-21 12:09 ` Andi Kleen
2010-11-21 12:22   ` Stephane Eranian
2010-11-21 14:19     ` Lin Ming
2010-11-21 16:52     ` Andi Kleen
2010-11-23  9:18       ` Stephane Eranian
2010-11-21 17:45     ` Peter Zijlstra
2010-11-21 18:28       ` Andi Kleen
2010-11-21 18:30         ` Peter Zijlstra [this message]
2010-11-21 14:12   ` Lin Ming

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=1290364238.2153.89.camel@laptop \
    --to=a.p.zijlstra@chello.nl \
    --cc=andi@firstfloor.org \
    --cc=arjan@infradead.org \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=mingo@elte.hu \
    /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