public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrii Nakryiko <andrii@kernel.org>
To: x86@kernel.org, peterz@infradead.org, mingo@redhat.com,
	tglx@linutronix.de
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
	jolsa@kernel.org, song@kernel.org, kernel-team@meta.com,
	Andrii Nakryiko <andrii@kernel.org>,
	Sandipan Das <sandipan.das@amd.com>
Subject: [PATCH v5 1/4] perf/x86/amd: ensure amd_pmu_core_disable_all() is always inlined
Date: Mon,  1 Apr 2024 19:21:15 -0700	[thread overview]
Message-ID: <20240402022118.1046049-2-andrii@kernel.org> (raw)
In-Reply-To: <20240402022118.1046049-1-andrii@kernel.org>

In the following patches we will enable LBR capture on AMD CPUs at
arbitrary point in time, which means that LBR recording won't be frozen
by hardware automatically as part of hardware overflow event. So we need
to take care to minimize amount of branches and function calls/returns
on the path to freezing LBR, minimizing LBR snapshot altering as much as
possible.

amd_pmu_core_disable_all() is one of the functions on this path, and is
already marked as __always_inline. But it calls amd_pmu_set_global_ctl()
which is marked as just inline.  So to guarantee no function call will
be generated thoughout mark amd_pmu_set_global_ctl() as __always_inline
as well.

Reviewed-by: Sandipan Das <sandipan.das@amd.com>
Signed-off-by: Andrii Nakryiko <andrii@kernel.org>
---
 arch/x86/events/amd/core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/x86/events/amd/core.c b/arch/x86/events/amd/core.c
index 985ef3b47919..9b15afda0326 100644
--- a/arch/x86/events/amd/core.c
+++ b/arch/x86/events/amd/core.c
@@ -647,7 +647,7 @@ static void amd_pmu_cpu_dead(int cpu)
 	}
 }
 
-static inline void amd_pmu_set_global_ctl(u64 ctl)
+static __always_inline void amd_pmu_set_global_ctl(u64 ctl)
 {
 	wrmsrl(MSR_AMD64_PERF_CNTR_GLOBAL_CTL, ctl);
 }
-- 
2.43.0


  reply	other threads:[~2024-04-02  2:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02  2:21 [PATCH v5 0/4] perf/x86/amd: add LBR capture support outside of hardware events Andrii Nakryiko
2024-04-02  2:21 ` Andrii Nakryiko [this message]
2024-04-03  7:40   ` [tip: perf/core] perf/x86/amd: Ensure amd_pmu_core_disable_all() is always inlined tip-bot2 for Andrii Nakryiko
2024-04-02  2:21 ` [PATCH v5 2/4] perf/x86/amd: avoid taking branches before disabling LBR Andrii Nakryiko
2024-04-03  7:40   ` [tip: perf/core] perf/x86/amd: Avoid " tip-bot2 for Andrii Nakryiko
2024-04-02  2:21 ` [PATCH v5 3/4] perf/x86/amd: support capturing LBR from software events Andrii Nakryiko
2024-04-03  7:40   ` [tip: perf/core] perf/x86/amd: Support " tip-bot2 for Andrii Nakryiko
2024-04-02  2:21 ` [PATCH v5 4/4] perf/x86/amd: don't reject non-sampling events with configured LBR Andrii Nakryiko
2024-04-03  7:40   ` [tip: perf/core] perf/x86/amd: Don't " tip-bot2 for Andrii Nakryiko
2024-04-03  7:19 ` [PATCH v5 0/4] perf/x86/amd: add LBR capture support outside of hardware events Ingo Molnar

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=20240402022118.1046049-2-andrii@kernel.org \
    --to=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=jolsa@kernel.org \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=sandipan.das@amd.com \
    --cc=song@kernel.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