From: "Liang, Kan" <kan.liang@linux.intel.com>
To: lirongqing <lirongqing@baidu.com>,
peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com, tglx@linutronix.de,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/x86/intel/bts: allocate bts_ctx only if necessary
Date: Thu, 23 Jan 2025 13:54:42 -0500 [thread overview]
Message-ID: <1f213692-197e-4f14-a0e8-3d825beabfa3@linux.intel.com> (raw)
In-Reply-To: <20250122074103.3091-1-lirongqing@baidu.com>
On 2025-01-22 2:41 a.m., lirongqing wrote:
> From: Li RongQing <lirongqing@baidu.com>
>
> Avoid unnecessary per-CPU memory allocation on unsupported CPUs,
> this can save 12K memory for each CPU
>
> Signed-off-by: Li RongQing <lirongqing@baidu.com>
Acked-by: Kan Liang <kan.liang@linux.intel.com>
Thanks,
Kan
> ---
> arch/x86/events/intel/bts.c | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
>
> diff --git a/arch/x86/events/intel/bts.c b/arch/x86/events/intel/bts.c
> index 8f78b0c..8e09319 100644
> --- a/arch/x86/events/intel/bts.c
> +++ b/arch/x86/events/intel/bts.c
> @@ -36,7 +36,7 @@ enum {
> BTS_STATE_ACTIVE,
> };
>
> -static DEFINE_PER_CPU(struct bts_ctx, bts_ctx);
> +static struct bts_ctx __percpu *bts_ctx;
>
> #define BTS_RECORD_SIZE 24
> #define BTS_SAFETY_MARGIN 4080
> @@ -231,7 +231,7 @@ bts_buffer_reset(struct bts_buffer *buf, struct perf_output_handle *handle);
>
> static void __bts_event_start(struct perf_event *event)
> {
> - struct bts_ctx *bts = this_cpu_ptr(&bts_ctx);
> + struct bts_ctx *bts = this_cpu_ptr(bts_ctx);
> struct bts_buffer *buf = perf_get_aux(&bts->handle);
> u64 config = 0;
>
> @@ -260,7 +260,7 @@ static void __bts_event_start(struct perf_event *event)
> static void bts_event_start(struct perf_event *event, int flags)
> {
> struct cpu_hw_events *cpuc = this_cpu_ptr(&cpu_hw_events);
> - struct bts_ctx *bts = this_cpu_ptr(&bts_ctx);
> + struct bts_ctx *bts = this_cpu_ptr(bts_ctx);
> struct bts_buffer *buf;
>
> buf = perf_aux_output_begin(&bts->handle, event);
> @@ -290,7 +290,7 @@ static void bts_event_start(struct perf_event *event, int flags)
>
> static void __bts_event_stop(struct perf_event *event, int state)
> {
> - struct bts_ctx *bts = this_cpu_ptr(&bts_ctx);
> + struct bts_ctx *bts = this_cpu_ptr(bts_ctx);
>
> /* ACTIVE -> INACTIVE(PMI)/STOPPED(->stop()) */
> WRITE_ONCE(bts->state, state);
> @@ -305,7 +305,7 @@ static void __bts_event_stop(struct perf_event *event, int state)
> static void bts_event_stop(struct perf_event *event, int flags)
> {
> struct cpu_hw_events *cpuc = this_cpu_ptr(&cpu_hw_events);
> - struct bts_ctx *bts = this_cpu_ptr(&bts_ctx);
> + struct bts_ctx *bts = this_cpu_ptr(bts_ctx);
> struct bts_buffer *buf = NULL;
> int state = READ_ONCE(bts->state);
>
> @@ -338,7 +338,7 @@ static void bts_event_stop(struct perf_event *event, int flags)
>
> void intel_bts_enable_local(void)
> {
> - struct bts_ctx *bts = this_cpu_ptr(&bts_ctx);
> + struct bts_ctx *bts = this_cpu_ptr(bts_ctx);
> int state = READ_ONCE(bts->state);
>
> /*
> @@ -358,7 +358,7 @@ void intel_bts_enable_local(void)
>
> void intel_bts_disable_local(void)
> {
> - struct bts_ctx *bts = this_cpu_ptr(&bts_ctx);
> + struct bts_ctx *bts = this_cpu_ptr(bts_ctx);
>
> /*
> * Here we transition from ACTIVE to INACTIVE;
> @@ -450,7 +450,7 @@ bts_buffer_reset(struct bts_buffer *buf, struct perf_output_handle *handle)
> int intel_bts_interrupt(void)
> {
> struct debug_store *ds = this_cpu_ptr(&cpu_hw_events)->ds;
> - struct bts_ctx *bts = this_cpu_ptr(&bts_ctx);
> + struct bts_ctx *bts = this_cpu_ptr(bts_ctx);
> struct perf_event *event = bts->handle.event;
> struct bts_buffer *buf;
> s64 old_head;
> @@ -518,7 +518,7 @@ static void bts_event_del(struct perf_event *event, int mode)
>
> static int bts_event_add(struct perf_event *event, int mode)
> {
> - struct bts_ctx *bts = this_cpu_ptr(&bts_ctx);
> + struct bts_ctx *bts = this_cpu_ptr(bts_ctx);
> struct cpu_hw_events *cpuc = this_cpu_ptr(&cpu_hw_events);
> struct hw_perf_event *hwc = &event->hw;
>
> @@ -605,6 +605,10 @@ static __init int bts_init(void)
> return -ENODEV;
> }
>
> + bts_ctx = alloc_percpu(struct bts_ctx);
> + if (!bts_ctx)
> + return -ENOMEM;
> +
> bts_pmu.capabilities = PERF_PMU_CAP_AUX_NO_SG | PERF_PMU_CAP_ITRACE |
> PERF_PMU_CAP_EXCLUSIVE;
> bts_pmu.task_ctx_nr = perf_sw_context;
next prev parent reply other threads:[~2025-01-23 18:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 7:41 [PATCH] perf/x86/intel/bts: allocate bts_ctx only if necessary lirongqing
2025-01-23 18:36 ` Adrian Hunter
2025-01-23 18:54 ` Liang, Kan [this message]
2025-03-05 13:47 ` Jiri Olsa
2025-03-05 13:54 ` Jiri Olsa
2025-03-05 14:58 ` Adrian Hunter
2025-03-05 16:11 ` Dave Hansen
2025-03-06 2:28 ` 答复: [外部邮件] " Li,Rongqing
[not found] <20241030063521.4025-1-lirongqing@baidu.com>
2024-10-30 7:26 ` Alexander Shishkin
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=1f213692-197e-4f14-a0e8-3d825beabfa3@linux.intel.com \
--to=kan.liang@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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 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).