From: Peter Zijlstra <peterz@infradead.org>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: tglx@linutronix.de, fenghua.yu@intel.com, tony.luck@intel.com,
mingo@redhat.com, acme@kernel.org, gavin.hindman@intel.com,
jithu.joseph@intel.com, dave.hansen@intel.com, hpa@zytor.com,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 2/6] perf/core: Add helper to obtain performance counter index
Date: Tue, 18 Sep 2018 01:07:58 +0200 [thread overview]
Message-ID: <20180917230758.GA3117@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <fdb736aa-3c2a-67d3-473f-b5a2a7d2c0e5@intel.com>
On Mon, Sep 17, 2018 at 09:37:14AM -0700, Reinette Chatre wrote:
> On 9/17/2018 1:23 AM, Peter Zijlstra wrote:
> > I said arch/x86/include/asm/perf_events.h and call it:
> > x86_perf_rdpmc_index().
> >
> > This function is very much x86 specific.
> Moving it to arch/x86/include/asm/perf_event.h is not trivial since this
> file is not familiar with struct perf_event.
Urgh, right you are. Does it work if you make it a regular function
instead of an inline? Put the thing in arch/x86/events/core.c or so and
only an extern decl in asm/perf_event.h.
next prev parent reply other threads:[~2018-09-17 23:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 17:14 [PATCH V3 0/6] perf/core and x86/intel_rdt: Fix lack of coordination with perf Reinette Chatre
2018-09-11 17:14 ` [PATCH V3 1/6] perf/core: Add sanity check to deal with pinned event failure Reinette Chatre
2018-09-11 17:14 ` [PATCH V3 2/6] perf/core: Add helper to obtain performance counter index Reinette Chatre
2018-09-17 8:23 ` Peter Zijlstra
2018-09-17 16:37 ` Reinette Chatre
2018-09-17 23:07 ` Peter Zijlstra [this message]
2018-09-18 17:54 ` Reinette Chatre
2018-09-19 9:17 ` Peter Zijlstra
2018-09-11 17:14 ` [PATCH V3 3/6] x86/intel_rdt: Remove local register variables Reinette Chatre
2018-09-11 17:14 ` [PATCH V3 4/6] x86/intel_rdt: Create required perf event attributes Reinette Chatre
2018-09-12 5:49 ` kbuild test robot
2018-09-12 7:20 ` kbuild test robot
2018-09-12 19:54 ` [PATCH V4 " Reinette Chatre
2018-09-11 17:14 ` [PATCH V3 5/6] x86/intel_rdt: Use perf infrastructure for measurements Reinette Chatre
2018-09-17 8:58 ` Peter Zijlstra
2018-09-17 16:54 ` Reinette Chatre
2018-09-11 17:14 ` [PATCH V3 6/6] x86/intel_rdt: Re-enable pseudo-lock measurements Reinette Chatre
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=20180917230758.GA3117@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=dave.hansen@intel.com \
--cc=fenghua.yu@intel.com \
--cc=gavin.hindman@intel.com \
--cc=hpa@zytor.com \
--cc=jithu.joseph@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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 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.