From: Peter Zijlstra <peterz@infradead.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/5] perf: Add ioctl to emit sideband events
Date: Mon, 17 Apr 2023 13:02:21 +0200 [thread overview]
Message-ID: <20230417110221.GH83892@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20230414082300.34798-1-adrian.hunter@intel.com>
On Fri, Apr 14, 2023 at 11:22:55AM +0300, Adrian Hunter wrote:
> Hi
>
> Here is a stab at adding an ioctl for sideband events.
>
> This is to overcome races when reading the same information
> from /proc.
What races? Are you talking about reading old state in /proc the kernel
delivering a sideband event for the new state, and then you writing the
old state out?
Surely that's something perf tool can fix without kernel changes?
next prev parent reply other threads:[~2023-04-17 11:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 8:22 [PATCH RFC 0/5] perf: Add ioctl to emit sideband events Adrian Hunter
2023-04-14 8:22 ` [PATCH RFC 1/5] " Adrian Hunter
2023-04-17 10:57 ` Peter Zijlstra
2023-04-18 6:29 ` Adrian Hunter
2023-04-14 8:22 ` [PATCH RFC 2/5] perf: Add fork to the sideband ioctl Adrian Hunter
2023-04-14 8:22 ` [PATCH RFC 3/5] perf: Add namespaces " Adrian Hunter
2023-04-14 8:22 ` [PATCH RFC 4/5] perf: Add comm " Adrian Hunter
2023-04-14 8:23 ` [PATCH RFC 5/5] perf: Add mmap " Adrian Hunter
2023-04-17 11:02 ` Peter Zijlstra [this message]
2023-04-17 16:37 ` [PATCH RFC 0/5] perf: Add ioctl to emit sideband events Ian Rogers
2023-04-18 7:03 ` Adrian Hunter
2023-04-18 6:18 ` Adrian Hunter
2023-04-18 13:36 ` Adrian Hunter
2023-04-18 15:51 ` Ian Rogers
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=20230417110221.GH83892@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--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 \
/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