mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Stephane Eranian <eranian@gmail.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: perf/Documentation/ABI -- add some documentation for perf_event sysfs usage
Date: Thu, 4 Jul 2013 11:02:53 +0200	[thread overview]
Message-ID: <20130704090253.GJ18898@dyad.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1307032308040.13409@vincent-weaver-1.um.maine.edu>

On Wed, Jul 03, 2013 at 11:14:40PM -0400, Vince Weaver wrote:
> On Wed, 3 Jul 2013, Vince Weaver wrote:

> OK, don't I feel silly, these values were already documented in 
>    Documentation/ABI/testing/sysfs-bus-event_source-devices-events
> rather than ABI/stable
> 
> To be fair I missed it because the documentation seemed to come from the 
> Power developers and not through perf_event
>
> anyway, that documentation says the values will be hex only, which was 
> broken by
> 
> commit f9134f36aed59ab55c0ab1a4618dd455f15aef5f
> Author: Andi Kleen <ak@linux.intel.com>
> Date:   Mon Jun 17 17:36:52 2013 -0700
> 
>     perf/x86/intel: Add mem-loads/stores support for Haswell
> 
> 
> which added:
> EVENT_ATTR_STR(mem-loads,      mem_ld_hsw,     "event=0xcd,umask=0x1,ldlat=3");
> 
> (note ldlat is not in hex).
> 
> This broke the trinity fuzzer (which scans to look for events to use)
> as well as some of my personal tools.
> 
> Should the ldlat value be fixed to be hex?  Or should we ammend the ABI
> document to allow decimal?

I don't see a good reason not to allow decimal as well. Jolsa?

  reply	other threads:[~2013-07-04  9:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 19:39 Vince Weaver
2013-07-04  3:14 ` Vince Weaver
2013-07-04  9:02   ` Peter Zijlstra [this message]
2013-07-04 22:02     ` Jiri Olsa
2013-07-05 15:28       ` Vince Weaver
2013-07-07 14:56         ` Jiri Olsa

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=20130704090253.GJ18898@dyad.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@ghostprotocols.net \
    --cc=ak@linux.intel.com \
    --cc=eranian@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulus@samba.org \
    --cc=vincent.weaver@maine.edu \
    /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

all inboxes | Powered by JetHome®