From: Jiri Olsa <jolsa@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: acme@redhat.com, a.p.zijlstra@chello.nl, mingo@elte.hu,
paulus@samba.org, cjashfor@linux.vnet.ibm.com,
fweisbec@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] perf, x86: Making hardware events translations available in sysfs
Date: Mon, 20 Aug 2012 11:55:39 +0200 [thread overview]
Message-ID: <20120820095539.GA1176@krava.brq.redhat.com> (raw)
In-Reply-To: <CABPqkBQ7ZFw2c706JwvMVq1i1LCGo4108MCvynMqpXkPCbk39g@mail.gmail.com>
On Mon, Aug 20, 2012 at 10:25:42AM +0200, Stephane Eranian wrote:
> On Mon, Jul 9, 2012 at 10:37 PM, Jiri Olsa <jolsa@redhat.com> wrote:
SNIP
> > +static ssize_t event_sysfs_data(char *page, u64 config)
> > +{
> > + u64 event = (config & ARCH_PERFMON_EVENTSEL_EVENT) |
> > + (config & AMD64_EVENTSEL_EVENT) >> 24;
> > + u64 umask = (config & ARCH_PERFMON_EVENTSEL_UMASK) >> 8;
> > + u64 inv = (config & ARCH_PERFMON_EVENTSEL_INV) >> 23;
> > + u64 cmask = (config & ARCH_PERFMON_EVENTSEL_CMASK) >> 24;
> > + ssize_t ret;
> > +
> > + /*
> > + * We have whole page size to spend and just little data
> > + * to write, so we can safely use sprintf.
> > + */
> > + ret = sprintf(page, "event=0x%02llx", event);
> > +
> > + if (umask)
> > + ret += sprintf(page + ret, ",umask=0x%02llx", umask);
> > +
> > + if (inv)
> > + ret += sprintf(page + ret, ",inv");
> > +
> > + if (cmask)
> > + ret += sprintf(page + ret, ",cmask=0x%02llx", cmask);
> > +
>
> You are not handling the model specific modifiers such as any_thread on Intel.
> It's not used right now. But you should handle the case now. That will avoid
> problems in the future.
ok, will add those
>
> > + ret += sprintf(page + ret, "\n");
> > +
> > + return ret;
> > +}
SNIP
> > static const struct attribute_group *x86_pmu_attr_groups[] = {
> > &x86_pmu_attr_group,
> > &x86_pmu_format_group,
> > + &x86_pmu_events_group,
> > NULL,
> > };
> >
> You are not checking whether or not the generic event is even available on the
> host core PMU. You don't want to expose generic events which are not available.
thats what patch 2 does
> And if you do this, then you need to take care of the other arch as well. They
> also deserve the extended syntax.
hm, I could try to add something for ppc, but that's where my arch
hw availability ends
thanks,
jirka
next prev parent reply other threads:[~2012-08-20 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 20:37 [PATCHv3 0/6] perf, tool: Allow to use hw events in PMU syntax Jiri Olsa
2012-07-09 20:37 ` [PATCH 1/6] perf, x86: Making hardware events translations available in sysfs Jiri Olsa
2012-08-20 8:25 ` Stephane Eranian
2012-08-20 9:55 ` Jiri Olsa [this message]
2012-07-09 20:37 ` [PATCH 2/6] perf, x86: Filter out undefined events from sysfs events attribute Jiri Olsa
2012-07-09 20:37 ` [PATCH 3/6] perf, tool: Fix pmu object alias initialization Jiri Olsa
2012-07-09 20:37 ` [PATCH 4/6] perf, tool: Properly free format data Jiri Olsa
2012-07-09 20:37 ` [PATCH 5/6] perf, tool: Add support to specify hw event as pmu event term Jiri Olsa
2012-07-09 20:37 ` [PATCH 6/6] perf, test: Add automated tests for pmu sysfs translated events Jiri Olsa
2012-08-08 12:42 ` [PATCHv3 0/6] perf, tool: Allow to use hw events in PMU syntax Jiri Olsa
2012-08-16 13:44 ` 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=20120820095539.GA1176@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®