From: Maciej Patelczyk <maciej.patelczyk@intel.com>
To: Jan Maslak <jan.maslak@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH 0/2] tests/intel/xe_eudebug_online: Fix sporadic failures due to unhandled fsync errors
Date: Thu, 7 May 2026 11:11:52 +0200 [thread overview]
Message-ID: <50f95966-a5a4-4ef6-a7ae-484ed0272ac3@intel.com> (raw)
In-Reply-To: <20260304143619.3854871-1-jan.maslak@intel.com>
On 04/03/2026 15:36, Jan Maslak wrote:
> Fix sporadic failures in xe_eudebug_online pagefault tests caused by
> fsync() on the debugger VM fd silently failing when the GPU cache flush
> hardware is temporarily busy.
>
> v2: Use IGT specific VM_SYNC_TIMEOUT_NS constant instead of
> DRM_XE_EUDEBUG_VM_SYNC_MAX_TIMEOUT_NSECS.
>
> Jan Maslak (2):
> tests/intel/xe_eudebug_online: Set timeout for debugger VM fd sync
> tests/intel/xe_eudebug_online: Assert fsync return on debugger VM fd
>
> tests/intel/xe_eudebug_online.c | 16 +++++++++-------
> 1 file changed, 9 insertions(+), 7 deletions(-)
>
Nice one,
Reviewed-by: Maciej Patelczyk <maciej.patelczyk@intel.com>
next prev parent reply other threads:[~2026-05-07 9:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 14:36 [PATCH 0/2] tests/intel/xe_eudebug_online: Fix sporadic failures due to unhandled fsync errors Jan Maslak
2026-03-04 14:36 ` [PATCH 1/2] tests/intel/xe_eudebug_online: Set timeout for debugger VM fd sync Jan Maslak
2026-03-04 14:36 ` [PATCH 2/2] tests/intel/xe_eudebug_online: Assert fsync return on debugger VM fd Jan Maslak
2026-03-05 7:12 ` ✓ i915.CI.BAT: success for tests/intel/xe_eudebug_online: Fix sporadic failures due to unhandled fsync errors (rev2) Patchwork
2026-03-05 12:16 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-05 18:28 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-07 9:11 ` Maciej Patelczyk [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-27 11:41 [PATCH 0/2] tests/intel/xe_eudebug_online: Fix sporadic failures due to unhandled fsync errors Jan Maslak
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=50f95966-a5a4-4ef6-a7ae-484ed0272ac3@intel.com \
--to=maciej.patelczyk@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jan.maslak@intel.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