From: James Clark <james.clark@arm.com>
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org
Cc: linux-perf-users@vger.kernel.org, leo.yan@linaro.com,
Suzuki.Poulose@arm.com, James Clark <james.clark@arm.com>,
linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/1] perf/core: Wake up parent event if inherited event has no ring buffer
Date: Mon, 6 Dec 2021 11:38:39 +0000 [thread overview]
Message-ID: <20211206113840.130802-1-james.clark@arm.com> (raw)
This is one possible fix to the issue described in the commit message.
What I'm not sure about is whether these other two possibilities should
be done instead, which is what I'm looking for feedback on:
* Assign the ring buffer of the parent event to the child in inherit_event()
* Move the poll list from the RB to the event, although it was moved into
the RB for a specific reason in 10c6db1
James Clark (1):
perf/core: Wake up parent event if inherited event has no ring buffer
kernel/events/core.c | 3 +++
1 file changed, 3 insertions(+)
--
2.28.0
next reply other threads:[~2021-12-06 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 11:38 James Clark [this message]
2021-12-06 11:38 ` [RFC PATCH 1/1] perf/core: Wake up parent event if inherited event has no ring buffer James Clark
2022-01-24 11:37 ` Ruben Ayrapetyan
2022-01-24 11:49 ` Peter Zijlstra
2022-01-24 14:58 ` James Clark
2022-01-25 19:12 ` Peter Zijlstra
2022-01-26 16:15 ` James Clark
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=20211206113840.130802-1-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=Suzuki.Poulose@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=leo.yan@linaro.com \
--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 \
/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).