From: Jiri Olsa <jolsa@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"ak@linux.intel.com" <ak@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
"Yan, Zheng" <zheng.z.yan@intel.com>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [PATCH v3 1/4] perf: add active_entry list head to struct perf_event
Date: Sat, 26 Oct 2013 19:44:26 +0200 [thread overview]
Message-ID: <20131026174426.GD1069@krava.brq.redhat.com> (raw)
In-Reply-To: <CABPqkBTHnRXwKVJucKRuPA1cLzKur2dbkKu_PS5sQKK2XjovnQ@mail.gmail.com>
On Sat, Oct 26, 2013 at 06:57:37PM +0200, Stephane Eranian wrote:
> On Fri, Oct 25, 2013 at 4:56 PM, Jiri Olsa <jolsa@redhat.com> wrote:
> >
> > On Wed, Oct 23, 2013 at 02:58:02PM +0200, Stephane Eranian wrote:
> > > This patch adds a new fields to the struct perf_event.
> > > It is intended to be used to chain events which are
> > > active (enabled). It helps in the hardware layer
> > > for PMU which do not have actual counter restrictions, i.e.,
> > > free running read-only counters. Active events are chained
> > > as opposed to being tracked via the counter they use.
> > >
> > > Signed-off-by: Stephane Eranian <eranian@google.com>
> > > ---
> > > include/linux/perf_event.h | 1 +
> > > kernel/events/core.c | 1 +
> > > 2 files changed, 2 insertions(+)
> > >
> > > diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h
> > > index 2e069d1..a376384 100644
> > > --- a/include/linux/perf_event.h
> > > +++ b/include/linux/perf_event.h
> > > @@ -435,6 +435,7 @@ struct perf_event {
> > > struct perf_cgroup *cgrp; /* cgroup event is attach to */
> > > int cgrp_defer_enabled;
> > > #endif
> > > + struct list_head active_entry;
> >
> > Could this be in union with 'hlist_entry' ? It looks
> > as 'same purpose' and 'mutualy exclusive stuff.
> >
> You're saying that I could use the hlist_entry field because
> it is currently only used by the sw events in the generic layer.
> But it seems to be a complicated rcu list for the purpose here.
nope, I just meant saving little space like:
union {
struct list_head active_entry;
struct hlist_node hlist_entry;
}
just a nitpick
jirka
next prev parent reply other threads:[~2013-10-26 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 12:58 [PATCH v3 0/4] perf,x86: add Intel RAPL PMU support Stephane Eranian
2013-10-23 12:58 ` [PATCH v3 1/4] perf: add active_entry list head to struct perf_event Stephane Eranian
2013-10-25 14:56 ` Jiri Olsa
2013-10-26 16:57 ` Stephane Eranian
2013-10-26 17:44 ` Jiri Olsa [this message]
2013-10-28 9:58 ` Stephane Eranian
2013-10-23 12:58 ` [PATCH v3 2/4] perf stat: add event unit and scale support Stephane Eranian
2013-10-23 12:58 ` [PATCH v3 3/4] perf,x86: add Intel RAPL PMU support Stephane Eranian
2013-10-25 11:13 ` Jiri Olsa
2013-10-25 11:13 ` Jiri Olsa
2013-10-25 11:14 ` Jiri Olsa
2013-10-26 17:00 ` Stephane Eranian
2013-10-28 10:33 ` Stephane Eranian
2013-10-28 12:17 ` Peter Zijlstra
2013-10-28 15:54 ` Stephane Eranian
2013-10-23 12:58 ` [PATCH v3 4/4] perf,x86: add RAPL hrtimer support Stephane Eranian
2013-10-25 17:44 ` Jiri Olsa
2013-10-26 17:07 ` Stephane Eranian
2013-10-26 17:53 ` Jiri Olsa
2013-10-28 9:55 ` Stephane Eranian
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=20131026174426.GD1069@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=zheng.z.yan@intel.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.