From: Peter Zijlstra <peterz@infradead.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>,
Kan Liang <kan.liang@linux.intel.com>,
Ravi Bangoria <ravi.bangoria@amd.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] perf/core: Introduce cpuctx->cgrp_ctx_list
Date: Wed, 11 Oct 2023 09:51:36 +0200 [thread overview]
Message-ID: <20231011075136.GM14330@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <CAM9d7cjxSd9QJzTs1_s6Nh7c38FZ7_2FGPoCunvnmjX_y-+Dyg@mail.gmail.com>
On Tue, Oct 10, 2023 at 08:45:03PM -0700, Namhyung Kim wrote:
> On Mon, Oct 9, 2023 at 9:57 PM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > Hi Peter,
> >
> > On Mon, Oct 9, 2023 at 2:04 PM Peter Zijlstra <peterz@infradead.org> wrote:
> > >
> > > On Wed, Oct 04, 2023 at 09:32:24AM -0700, Namhyung Kim wrote:
> > >
> > > > Yeah, I know.. but I couldn't come up with a better solution.
> > >
> > > Not been near a compiler, and haven't fully thought it through, but
> > > could something like the work work?
> >
> > Thanks for the patch, I think it'd work. Let me test it
> > and get back to you.
>
> I worked well but contained a typo. See below.
Ha, typing hard ;-) I did say it hadn't been near a compiler ...
> Which way do you want to process this change? Do I send it again
> with your S-o-b or will you apply it by yourself? Either is fine, just
> let me know. In case of latter, you can add
I'll go write me a Changelog and apply the thing, then we can forget
about things.
next prev parent reply other threads:[~2023-10-11 7:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 4:08 [PATCH] perf/core: Introduce cpuctx->cgrp_ctx_list Namhyung Kim
2023-10-04 7:26 ` Ingo Molnar
2023-10-04 15:01 ` Namhyung Kim
2023-10-04 15:42 ` Ingo Molnar
2023-10-04 21:27 ` Namhyung Kim
2023-10-04 16:02 ` Peter Zijlstra
2023-10-04 16:32 ` Namhyung Kim
2023-10-09 21:04 ` Peter Zijlstra
2023-10-10 4:57 ` Namhyung Kim
2023-10-11 3:45 ` Namhyung Kim
2023-10-11 7:51 ` Peter Zijlstra [this message]
2023-10-11 9:50 ` Peter Zijlstra
2023-10-11 16:02 ` Namhyung Kim
2023-10-12 17:34 ` [tip: perf/core] perf: Optimize perf_cgroup_switch() tip-bot2 for 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=20231011075136.GM14330@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@amd.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.