From: Nick Alcock <nick.alcock@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: <dtrace@lists.linux.dev>, <dtrace-devel@oss.oracle.com>
Subject: Re: [PATCH 1/5] test: fbt return0: work on quiet systems
Date: Tue, 07 Oct 2025 16:36:13 +0100 [thread overview]
Message-ID: <87v7kq4tci.fsf@esperi.org.uk> (raw)
In-Reply-To: <aOPpuSFUk1GWVokj@oracle.com> (Kris Van Hees's message of "Mon, 6 Oct 2025 12:09:29 -0400")
On 6 Oct 2025, Kris Van Hees spake thusly:
> On Mon, Oct 06, 2025 at 04:28:24PM +0100, Nick Alcock wrote:
>> These two tests probe on sys_poll and just hope something calls it.
>> On sufficiently quiet systems, nothing does.
>>
>> Define a trivial trigger to do so.
>
> Why not change the probe to be on hrtimer_nanosleep and use periodic_output
> as trigger, rather than adding another trigger executable?
Happy to. I wasn't sure if we depended on it being poll :)
Patch coming shortly.
--
NULL && (void)
next prev parent reply other threads:[~2025-10-07 15:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-06 15:28 [PATCH 1/5] test: fbt return0: work on quiet systems Nick Alcock
2025-10-06 15:28 ` [PATCH 2/5] test: nfs: don't require a locking daemon Nick Alcock
2025-10-06 16:11 ` Kris Van Hees
2025-10-06 15:28 ` [PATCH 3/5] test: preprocessor: work on GCC 16 Nick Alcock
2025-10-07 15:08 ` Kris Van Hees
2025-10-06 15:28 ` [PATCH 4/5] test: tid_pid: don't assume the type of pthread_t Nick Alcock
2025-10-06 16:13 ` Kris Van Hees
2025-10-06 15:28 ` [PATCH 5/5] test: dupstruct: fix extra duplicate identifier case Nick Alcock
2025-10-06 16:14 ` Kris Van Hees
2025-10-06 16:09 ` [PATCH 1/5] test: fbt return0: work on quiet systems Kris Van Hees
2025-10-07 15:36 ` Nick Alcock [this message]
2025-10-08 11:16 ` [PATCH v2 " Nick Alcock
2025-10-08 16:15 ` Kris Van Hees
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=87v7kq4tci.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=kris.van.hees@oracle.com \
/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