From: Lin Ming <ming.m.lin@intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/4] perf-events: Add support for supplementary event registers
Date: Wed, 02 Mar 2011 08:37:26 +0800 [thread overview]
Message-ID: <1299026246.4937.99.camel@minggr.sh.intel.com> (raw)
In-Reply-To: <AANLkTimvx+MYhOw8VFsJn4V6FQutKiYO6pHxgd9xGY8A@mail.gmail.com>
On Wed, 2011-03-02 at 01:09 +0800, Stephane Eranian wrote:
> Lin,
>
> See comments below:
>
> On Tue, Mar 1, 2011 at 5:47 PM, Lin Ming <ming.m.lin@intel.com> wrote:
> > From: Andi Kleen <ak@linux.intel.com>
> > static struct event_constraint *
> > +intel_percore_constraints(struct cpu_hw_events *cpuc, struct perf_event *event)
> > +{
> > + struct hw_perf_event *hwc = &event->hw;
> > + unsigned int e = hwc->config & ARCH_PERFMON_EVENTSEL_EVENT;
> > + struct event_constraint *c;
> > + struct intel_percore *pc;
> > + struct er_account *era;
> > + int i;
> > + int free_slot;
> > + int found;
> > +
> > + if (!x86_pmu.percore_constraints || hwc->extra_alloc)
> > + return NULL;
> > +
> > + for (c = x86_pmu.percore_constraints; c->cmask; c++) {
> > + if (e != c->code)
> > + continue;
> > +
> > + /*
> > + * Allocate resource per core.
> > + */
> > + c = NULL;
>
> Not sure I understand this c = NULL, given you hardcoded return NULL
> outside of the
> loop. I forgot to mention this earlier.
Right, that is redundant.
Remove it.
>
> > + pc = cpuc->per_core;
> > + if (!pc)
> > + break;
> > + c = &emptyconstraint;
> > + raw_spin_lock(&pc->lock);
> > + free_slot = -1;
> > + found = 0;
> > + for (i = 0; i < MAX_EXTRA_REGS; i++) {
> > + era = &pc->regs[i];
> > + if (era->ref > 0 && hwc->extra_reg == era->extra_reg) {
> > + /* Allow sharing same config */
> > + if (hwc->extra_config == era->extra_config) {
> > + era->ref++;
> > + cpuc->percore_used = 1;
> > + hwc->extra_alloc = 1;
> > + c = NULL;
> > + }
> > + /* else conflict */
> > + found = 1;
> > + break;
> > + } else if (era->ref == 0 && free_slot == -1)
> > + free_slot = i;
> > + }
> > + if (!found && free_slot != -1) {
> > + era = &pc->regs[free_slot];
> > + era->ref = 1;
> > + era->extra_reg = hwc->extra_reg;
> > + era->extra_config = hwc->extra_config;
> > + cpuc->percore_used = 1;
> > + hwc->extra_alloc = 1;
> > + c = NULL;
> > + }
> > + raw_spin_unlock(&pc->lock);
> > + return c;
> > + }
> > +
> > + return NULL;
> > +}
> > +
> > diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
> > index 8ceb5a6..48d966a 100644
> > --- a/include/linux/perf_event.h
> > +++ b/include/linux/perf_event.h
> > @@ -225,8 +225,14 @@ struct perf_event_attr {
> > };
> >
> > __u32 bp_type;
> > - __u64 bp_addr;
> > - __u64 bp_len;
> > + union {
> > + __u64 bp_addr;
> > + __u64 config1; /* extension of config0 */
> > + };
> > + union {
> > + __u64 bp_len;
> > + __u64 config2; /* extension of config1 */
> > + };
> > };
> >
> I don't see where those config0 or config1 are coming from.
config0 means perf_event_attr::config.
Peter suggested to extend the attr config space.
http://marc.info/?l=linux-kernel&m=129838808907525&w=2
next prev parent reply other threads:[~2011-03-02 0:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 16:47 [PATCH v2 1/4] perf-events: Add support for supplementary event registers Lin Ming
2011-03-01 17:09 ` Stephane Eranian
2011-03-02 0:37 ` Lin Ming [this message]
2011-03-02 7:48 ` Stephane Eranian
2011-03-02 10:34 ` Peter Zijlstra
2011-03-02 12:07 ` Stephane Eranian
2011-03-02 12:29 ` 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=1299026246.4937.99.camel@minggr.sh.intel.com \
--to=ming.m.lin@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--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