All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Robert Richter <robert.richter@amd.com>,
	Anton Blanchard <anton@au1.ibm.com>,
	linux-kernel@vger.kernel.org, eranian@google.com,
	acme@redhat.com, linuxppc-dev@ozlabs.org, paulus@samba.org,
	mpjohn@us.ibm.com, mingo@kernel.org, asharma@fb.com
Subject: Re: [RFC][PATCH] perf: Add a few generic stalled-cycles events
Date: Wed, 31 Oct 2012 08:22:17 +0100	[thread overview]
Message-ID: <1351668137.4047.38.camel@twins> (raw)
In-Reply-To: <20121031064056.GA12061@us.ibm.com>

On Tue, 2012-10-30 at 23:40 -0700, Sukadev Bhattiprolu wrote:
> So instead of the names I came up with in this patch, stalled-cycles-fixe=
d-point
> we could use the name used in the CPU spec - 'cmplu_stall_fxu' in the arc=
h
> specific code ?=20

You could, but I would advise against it. Human readable names are so
much more accessible.

WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: Robert Richter <robert.richter@amd.com>,
	acme@redhat.com, mingo@kernel.org, eranian@google.com,
	asharma@fb.com, Anton Blanchard <anton@au1.ibm.com>,
	paulus@samba.org, mpjohn@us.ibm.com, linuxppc-dev@ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] perf: Add a few generic stalled-cycles events
Date: Wed, 31 Oct 2012 08:22:17 +0100	[thread overview]
Message-ID: <1351668137.4047.38.camel@twins> (raw)
In-Reply-To: <20121031064056.GA12061@us.ibm.com>

On Tue, 2012-10-30 at 23:40 -0700, Sukadev Bhattiprolu wrote:
> So instead of the names I came up with in this patch, stalled-cycles-fixed-point
> we could use the name used in the CPU spec - 'cmplu_stall_fxu' in the arch
> specific code ? 

You could, but I would advise against it. Human readable names are so
much more accessible.

  reply	other threads:[~2012-10-31  7:22 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12  1:28 [RFC][PATCH] perf: Add a few generic stalled-cycles events Sukadev Bhattiprolu
2012-10-12  1:28 ` Sukadev Bhattiprolu
2012-10-15  5:26 ` Anshuman Khandual
2012-10-15  5:26   ` Anshuman Khandual
2012-10-15 15:55 ` Robert Richter
2012-10-15 15:55   ` Robert Richter
2012-10-15 17:23   ` Arun Sharma
2012-10-15 17:23     ` Arun Sharma
2012-10-16  5:28     ` Anshuman Khandual
2012-10-16  5:28       ` Anshuman Khandual
2012-10-16 10:08   ` Robert Richter
2012-10-16 10:08     ` Robert Richter
2012-10-16 12:21     ` Stephane Eranian
2012-10-16 12:21       ` Stephane Eranian
2012-10-19 17:05       ` Sukadev Bhattiprolu
2012-10-19 17:05         ` Sukadev Bhattiprolu
2012-10-16 18:31     ` Sukadev Bhattiprolu
2012-10-16 18:31       ` Sukadev Bhattiprolu
2012-10-24 12:27       ` Peter Zijlstra
2012-10-24 12:27         ` Peter Zijlstra
2012-10-31  6:40         ` Sukadev Bhattiprolu
2012-10-31  6:40           ` Sukadev Bhattiprolu
2012-10-31  7:22           ` Peter Zijlstra [this message]
2012-10-31  7:22             ` Peter Zijlstra

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=1351668137.4047.38.camel@twins \
    --to=peterz@infradead.org \
    --cc=acme@redhat.com \
    --cc=anton@au1.ibm.com \
    --cc=asharma@fb.com \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mingo@kernel.org \
    --cc=mpjohn@us.ibm.com \
    --cc=paulus@samba.org \
    --cc=robert.richter@amd.com \
    --cc=sukadev@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.