linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dapeng Mi <dapeng1.mi@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Kan Liang <kan.liang@linux.intel.com>,
	Like Xu <likexu@tencent.com>, Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	kvm@vger.kernel.org, linux-perf-users@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Zhenyu Wang <zhenyuw@linux.intel.com>,
	Zhang Xiong <xiong.y.zhang@intel.com>,
	Lv Zhiyuan <zhiyuan.lv@intel.com>,
	Yang Weijiang <weijiang.yang@intel.com>,
	Dapeng Mi <dapeng1.mi@intel.com>, Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH RFV v2 05/13] perf/core: Add function perf_event_create_group_kernel_counters()
Date: Wed, 9 Aug 2023 16:44:53 +0800	[thread overview]
Message-ID: <ZNNSBZIQERc/nZXQ@dmi-pnp-i7> (raw)
In-Reply-To: <20230808102127.GZ212435@hirez.programming.kicks-ass.net>

On Tue, Aug 08, 2023 at 12:21:27PM +0200, Peter Zijlstra wrote:
> Date: Tue, 8 Aug 2023 12:21:27 +0200
> From: Peter Zijlstra <peterz@infradead.org>
> Subject: Re: [PATCH RFV v2 05/13] perf/core: Add function
>  perf_event_create_group_kernel_counters()
> 
> On Tue, Aug 08, 2023 at 02:31:03PM +0800, Dapeng Mi wrote:
> > diff --git a/kernel/events/core.c b/kernel/events/core.c
> > index 15eb82d1a010..1877171e9590 100644
> > --- a/kernel/events/core.c
> > +++ b/kernel/events/core.c
> > @@ -12762,11 +12762,34 @@ perf_event_create_kernel_counter(struct perf_event_attr *attr, int cpu,
> >  				 struct task_struct *task,
> >  				 perf_overflow_handler_t overflow_handler,
> >  				 void *context)
> > +{
> > +	return perf_event_create_group_kernel_counters(attr, cpu, task,
> > +			NULL, overflow_handler, context);
> > +}
> > +EXPORT_SYMBOL_GPL(perf_event_create_kernel_counter);
> > +
> > +/**
> > + * perf_event_create_group_kernel_counters
> > + *
> > + * @attr: attributes of the counter to create
> > + * @cpu: cpu in which the counter is bound
> > + * @task: task to profile (NULL for percpu)
> > + * @group_leader: the group leader event of the created event
> > + * @overflow_handler: callback to trigger when we hit the event
> > + * @context: context data could be used in overflow_handler callback
> > + */
> > +struct perf_event *
> > +perf_event_create_group_kernel_counters(struct perf_event_attr *attr,
> > +					int cpu, struct task_struct *task,
> > +					struct perf_event *group_leader,
> > +					perf_overflow_handler_t overflow_handler,
> > +					void *context)
> 
> I would much prefer if you just add the argument to
> perf_event_create_kernel_counter(), there aren't *that* many users.

Sure. Thanks.

-- 
Thanks,
Dapeng Mi

  reply	other threads:[~2023-08-09  8:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08  6:30 [PATCH RFV v2 00/13] Enable fixed counter 3 and topdown perf metrics for vPMU Dapeng Mi
2023-08-08  6:30 ` [PATCH RFV v2 01/13] KVM: x86/pmu: Add Intel CPUID-hinted TopDown slots event Dapeng Mi
2023-08-08  6:31 ` [PATCH RFV v2 02/13] KVM: x86/pmu: Support PMU fixed counter 3 Dapeng Mi
2023-08-08  6:31 ` [PATCH RFV v2 03/13] perf/core: Add function perf_event_group_leader_check() Dapeng Mi
2023-08-08  6:31 ` [PATCH RFV v2 04/13] perf/core: Add function perf_event_move_group() Dapeng Mi
2023-08-08  6:31 ` [PATCH RFV v2 05/13] perf/core: Add function perf_event_create_group_kernel_counters() Dapeng Mi
2023-08-08 10:21   ` Peter Zijlstra
2023-08-09  8:44     ` Dapeng Mi [this message]
2023-08-08  6:31 ` [PATCH RFV v2 06/13] perf/x86: Fix typos and inconsistent indents in perf_event header Dapeng Mi
2023-08-08  6:31 ` [PATCH RFV v2 07/13] perf/x86: Add constraint for guest perf metrics event Dapeng Mi
2023-08-08  6:31 ` [PATCH RFV v2 08/13] perf/core: Add new function perf_event_topdown_metrics() Dapeng Mi
2023-08-08 20:16   ` kernel test robot
2023-08-08 20:16   ` kernel test robot
2023-08-08  6:31 ` [PATCH RFV v2 09/13] perf/x86/intel: Handle KVM virtual metrics event in perf system Dapeng Mi
2023-08-08  6:31 ` [PATCH RFV v2 10/13] KVM: x86/pmu: Extend pmc_reprogram_counter() to create group events Dapeng Mi
2023-08-08  6:31 ` [PATCH RFV v2 11/13] KVM: x86/pmu: Support topdown perf metrics feature Dapeng Mi
2023-08-08  6:31 ` [PATCH RFV v2 12/13] KVM: x86/pmu: Handle PERF_METRICS overflow Dapeng Mi
2023-08-08  6:31 ` [PATCH RFV v2 13/13] KVM: x86/pmu: Expose Topdown in MSR_IA32_PERF_CAPABILITIES Dapeng Mi

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=ZNNSBZIQERc/nZXQ@dmi-pnp-i7 \
    --to=dapeng1.mi@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dapeng1.mi@intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=likexu@tencent.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=seanjc@google.com \
    --cc=weijiang.yang@intel.com \
    --cc=xiong.y.zhang@intel.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhiyuan.lv@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).