linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Robert O'Callahan" <robert@ocallahan.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Kyle Huey <me@kylehuey.com>, Ian Rogers <irogers@google.com>,
	Kyle Huey <khuey@kylehuey.com>,
	 Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	 Namhyung Kim <namhyung@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	 Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	 Adrian Hunter <adrian.hunter@intel.com>,
	linux-perf-users@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] perf test: Test FASYNC with watermark wakeups.
Date: Sat, 24 Feb 2024 10:43:38 +1300	[thread overview]
Message-ID: <CAOp6jLZKZKyYrJrzjZ90ZdxzzuDV0wp+XS3Rzssd-kvZV45JSQ@mail.gmail.com> (raw)
In-Reply-To: <ZdjdAKIV39A-jpR5@x1>

(I work with Kyle.)

IMHO this is more of a bug fix than a feature. `man perf_event_open`
expects this to work already: "watermark: If set, have an overflow
notification happen when we cross the wakeup_watermark boundary" and
later "Alternatively, the overflow events can be captured via a signal
handler, by enabling I/O signaling".

Bug fixes need regression tests. Such tests should fail on any kernel
where the bug is present. It seems strange to expect each such test to
detect whether the bug "should be fixed" in the kernel it's running on
and skip when that's not the case. I haven't seen any other project
try to do this. Instead (as in kernel selftests) the tests, the code
under test, and any metadata about which tests are expected to pass
are all in the repository together and updated together.

It makes sense that tests for the code in tools/perf should not fail
on older kernels, given that the code in tools/perf is expected to
work on older kernels. But tests for bug fixes in the kernel itself
should be expected to fail on older kernels and therefore should live
somewhere else, IMHO.

Rob
-- 
Su ot deraeppa sah dna Rehtaf eht htiw saw hcihw, efil lanrete eht uoy
ot mialcorp ew dna, ti ot yfitset dna ti nees evah ew; deraeppa efil
eht. Efil fo Drow eht gninrecnoc mialcorp ew siht - dehcuot evah sdnah
ruo dna ta dekool evah ew hcihw, seye ruo htiw nees evah ew hcihw,
draeh evah ew hcihw, gninnigeb eht morf saw hcihw taht.

  reply	other threads:[~2024-02-23 21:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 17:52 [PATCH 1/2] perf/ring_buffer: Trigger FASYNC signals for watermark wakeups Kyle Huey
2024-02-21 17:52 ` [PATCH 2/2] perf test: Test FASYNC with " Kyle Huey
2024-02-21 18:35   ` Ian Rogers
2024-02-22 17:55     ` Kyle Huey
2024-02-22 18:32       ` Ian Rogers
2024-02-22 18:41         ` Kyle Huey
2024-02-22 19:44           ` Ian Rogers
2024-02-22 19:54       ` Arnaldo Carvalho de Melo
2024-02-23 17:35         ` Kyle Huey
2024-02-23 17:59           ` Arnaldo Carvalho de Melo
2024-02-23 21:43             ` Robert O'Callahan [this message]
2024-02-24  2:27               ` Namhyung Kim
2024-02-24 15:58               ` Arnaldo Carvalho de Melo
2024-02-23 18:01           ` Ian Rogers
2024-02-23 18:17             ` Arnaldo Carvalho de Melo

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=CAOp6jLZKZKyYrJrzjZ90ZdxzzuDV0wp+XS3Rzssd-kvZV45JSQ@mail.gmail.com \
    --to=robert@ocallahan.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=khuey@kylehuey.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=me@kylehuey.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).