From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Andrew Morton <akpm@linux-foundation.org>,
"David Hildenbrand (Arm)" <david@kernel.org>,
"Mike Rapoport (Microsoft)" <rppt@kernel.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
bpf@vger.kernel.org, regressions@lists.linux.dev,
Sasha Levin <sashal@kernel.org>,
Alexander Motin <alexander.motin@truenas.com>,
Ameer Hamza <ameer.hamza@truenas.com>,
"Caleb St. John" <caleb.stjohn@truenas.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] perf/core: track the perf mlock gift separately
Date: Thu, 15 Oct 2026 10:09:43 +0100 [thread overview]
Message-ID: <atCYFpm63elRyuw7@gremlin> (raw)
In-Reply-To: <20261015075817.GO2009045@noisy.programming.kicks-ass.net>
On Thu, Oct 15, 2026 at 09:58:17AM +0200, Peter Zijlstra wrote:
> On Sat, Oct 03, 2026 at 05:29:07PM +0100, Lorenzo Stoakes (ARM) wrote:
> > Resolve the issue by simply giving perf its own field separate from the
> > rest.
>
> So I'm a little confused by all this -- perf introduced this field,
> others jumped on and shit broke, so we fix perf instead of the others?
Yeah I think the blame really lies with the later users, and that send a trend
that led to further confusion (including myself, mea culpa!)
> Anyway, patch seems straight forward enough; and you added comment to
> the fields, which I suppose does clarify things some.
>
> I'll take it. Thanks!
Thanks, much appreciated! :)
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-10-15 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 16:29 [PATCH] perf/core: track the perf mlock gift separately Lorenzo Stoakes (ARM)
2026-10-03 17:56 ` sashiko-bot
2026-10-15 7:58 ` Peter Zijlstra
2026-10-15 9:09 ` Lorenzo Stoakes (ARM) [this message]
2026-10-15 9:27 ` Thorsten Leemhuis
2026-10-15 10:40 ` Peter Zijlstra
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=atCYFpm63elRyuw7@gremlin \
--to=ljs@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.motin@truenas.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ameer.hamza@truenas.com \
--cc=bpf@vger.kernel.org \
--cc=caleb.stjohn@truenas.com \
--cc=david@kernel.org \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=rppt@kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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