public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Joel Granados <joel.granados@kernel.org>
Cc: Kees Cook <kees@kernel.org>, Steven Rostedt <rostedt@goodmis.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
	Adrian Hunter <adrian.hunter@intel.com>,
	"Liang, Kan" <kan.liang@linux.intel.com>,
	"David S. Miller" <davem@davemloft.net>,
	Andreas Larsson <andreas@gaisler.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-trace-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, sparclinux@vger.kernel.org,
	linux-s390@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 5/8] events: Move perf_event sysctls into kernel/events
Date: Tue, 18 Feb 2025 11:35:07 +0100	[thread overview]
Message-ID: <20250218103507.GC40464@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20250218-jag-mv_ctltables-v1-5-cd3698ab8d29@kernel.org>

On Tue, Feb 18, 2025 at 10:56:21AM +0100, Joel Granados wrote:
> Move ctl tables to two files:
> * perf_event_{paranoid,mlock_kb,max_sample_rate} and
>   perf_cpu_time_max_percent into kernel/events/core.c
> * perf_event_max_{stack,context_per_stack} into
>   kernel/events/callchain.c
> 
> Make static variables and functions that are fully contained in core.c
> and callchain.cand remove them from include/linux/perf_event.h.
> Additionally six_hundred_forty_kb is moved to callchain.c.
> 
> Two new sysctl tables are added ({callchain,events_core}_sysctl_table)
> with their respective sysctl registration functions.
> 
> This is part of a greater effort to move ctl tables into their
> respective subsystems which will reduce the merge conflicts in
> kerenel/sysctl.c.
> 
> Signed-off-by: Joel Granados <joel.granados@kernel.org>

Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>

  reply	other threads:[~2025-02-18 10:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-18  9:56 [PATCH 0/8] sysctl: Move sysctls from kern_table into their respective subsystems Joel Granados
2025-02-18  9:56 ` [PATCH 1/8] panic: Move panic ctl tables into panic.c Joel Granados
2025-02-18  9:56 ` [PATCH 2/8] signal: Move signal ctl tables into signal.c Joel Granados
2025-02-18  9:56 ` [PATCH 3/8] ftrace: Move trace sysctls into trace.c Joel Granados
2025-03-04  1:44   ` Steven Rostedt
2025-03-06 10:15     ` Joel Granados
2025-02-18  9:56 ` [PATCH 4/8] stack_tracer: move sysctl registration to kernel/trace/trace.c Joel Granados
2025-03-04  1:47   ` Steven Rostedt
2025-03-06 10:37     ` Joel Granados
2025-02-18  9:56 ` [PATCH 5/8] events: Move perf_event sysctls into kernel/events Joel Granados
2025-02-18 10:35   ` Peter Zijlstra [this message]
2025-02-21 14:06   ` [tip: perf/core] perf/core: " tip-bot2 for Joel Granados
2025-02-27 11:51     ` Joel Granados
2025-02-18  9:56 ` [PATCH 6/8] sparc: mv sparc sysctls into their own file under arch/sparc/kernel Joel Granados
2025-02-18  9:56 ` [PATCH 7/8] s390: mv s390 sysctls into their own file under arch/s390 dir joel granados
2025-02-18 14:08   ` Heiko Carstens
2025-02-21  7:59     ` Joel Granados
2025-02-18  9:56 ` [PATCH 8/8] x86: Move sysctls into arch/x86 Joel Granados
2025-02-18 12:11   ` [tip: x86/core] " tip-bot2 for Joel Granados

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=20250218103507.GC40464@noisy.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=agordeev@linux.ibm.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=andreas@gaisler.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=gerald.schaefer@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=hpa@zytor.com \
    --cc=irogers@google.com \
    --cc=joel.granados@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=kees@kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=rafael@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=svens@linux.ibm.com \
    --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