From: Matthew Auld <matthew.auld@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Maarten Lankhorst" <dev@lankhorst.se>,
intel-xe@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.BAT: failure for series starting with [1/2] drm/xe: Remove extra spaces in xe_vm.c (rev2)
Date: Wed, 26 Mar 2025 17:51:28 +0000 [thread overview]
Message-ID: <f1efe4a4-0f50-43b5-b372-0cce561a8fd2@intel.com> (raw)
In-Reply-To: <99ca7aa9bdfd797ad52b43b770136a0dbbcda854.camel@linux.intel.com>
On 25/03/2025 19:05, Thomas Hellström wrote:
> Hi,
>
> On Tue, 2025-03-25 at 11:41 +0100, Maarten Lankhorst wrote:
>> Cc: Matthew Auld
>>
>> Hey,
>>
>> For peer-to-peer DMA-BUF, it can be beneficial to allow mapping
>> memory as uncached.
>> Initially I tried copying the caching on same-driver import from the
>> original BO.
>>
>> Thomas suggested that since memory access from discrete is always
>> coherent, the
>> check in xe_vm.c can be simplified from XE_IOCTL_DBG(xe, coh_mode ==
>> XE_COH_NONE)
>> to XE_IOCTL_DBG(xe, !ID_DGFX(xe) && coh_mode == XE_COH_NONE)
>>
>> This causes below failures.
>>
>> Should I continue with the original patch, or change the testcase as
>> well?
>
> This is a tricky one.
> But first, why aren't those tests failing similarly with the original
> patch?
>
> Also, If we were to use system dma-buf with the exported bo WB, then
> the app would fail anyway?
>
> Perhaps we should use a separate test for p2p dma-bufs (attach-
>> peer2peer), but then again UMD wouldn't know whether it's peer2peer or
> not.
>
> I think if we need to access cross-device bos for metadata, we need to
> check with Sima / Dave first. I don't think that's something that is
> encouraged, really.
If this is a concern, is it possible that we rather update the PAT table
encoding on dgpu to reflect that everything is really 1way on dgpu i.e
coh_none is not even a thing in the first place? Then we don't care
about XE_IOCTL_DBG(xe, coh_mode == XE_COH_NONE)? But maybe that's too bold.
>
> /Thomas
>
>
>
>
>
>
>>
>> Kind Regards,
>> ~Maarten
>>
>>
>> On 2025-03-25 10:37, Patchwork wrote:
>>> *Patch Details*
>>> *Series:* series starting with [1/2] drm/xe: Remove extra
>>> spaces in xe_vm.c (rev2)
>>> *URL:*
>>> https://patchwork.freedesktop.org/series/146562/ <https://patchwork
>>> .freedesktop.org/series/146562/>
>>> *State:* failure
>>> *Details:*
>>> https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146562v2/index.html
>>> <
>>> https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146562v2/index.html
>>>>
>>>
>>>
>>> CI Bug Log - changes from xe-2844-
>>> 9a42bdcde0f77b2c1e947e283cc3b267b1ce2056_BAT -> xe-pw-146562v2_BAT
>>>
>>>
>>> Summary
>>>
>>> *FAILURE*
>>>
>>> Serious unknown changes coming with xe-pw-146562v2_BAT absolutely
>>> need to be
>>> verified manually.
>>>
>>> If you think the reported changes have nothing to do with the
>>> changes
>>> introduced in xe-pw-146562v2_BAT, please notify your bug team
>>> (I915-ci-infra@lists.freedesktop.org) to allow them
>>> to document this new failure mode, which will reduce false
>>> positives in CI.
>>>
>>>
>>> Participating hosts (10 -> 9)
>>>
>>> Missing (1): bat-adlp-vm
>>>
>>>
>>> Possible new issues
>>>
>>> Here are the unknown changes that may have been introduced in xe-
>>> pw-146562v2_BAT:
>>>
>>>
>>> IGT changes
>>>
>>>
>>> Possible regressions
>>>
>>> * igt@xe_pat@prime-external-import-coh:
>>> o bat-bmg-2: PASS
>>> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-2844-9a42bdcde0f77b2c
>>> 1e947e283cc3b267b1ce2056/bat-bmg-2/igt@xe
>>> _pat@prime-external-import-coh.html> -> FAIL
>>> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146562v2/bat-bmg-2
>>> /igt@xe_pat@prime-external-import-coh.html>
>>> o bat-bmg-1: PASS
>>> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-2844-9a42bdcde0f77b2c
>>> 1e947e283cc3b267b1ce2056/bat-bmg-1/igt@xe
>>> _pat@prime-external-import-coh.html> -> FAIL
>>> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146562v2/bat-bmg-1
>>> /igt@xe_pat@prime-external-import-coh.html>
>>> o bat-dg2-oem2: PASS
>>> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-2844-9a42bdcde0f77b2c
>>> 1e947e283cc3b267b1ce2056/bat-dg2-oem2/igt@xe
>>> _pat@prime-external-import-coh.html> -> FAIL
>>> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146562v2/bat-dg2-o
>>> em2/igt@xe_pat@prime-external-import-coh.html>
>>> o bat-atsm-2: PASS
>>> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-2844-9a42bdcde0f77b2c
>>> 1e947e283cc3b267b1ce2056/bat-atsm-2/igt@xe
>>> _pat@prime-external-import-coh.html> -> FAIL
>>> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146562v2/bat-atsm
>>> -2/igt@xe_pat@prime-external-import-coh.html>
>>> o bat-pvc-2: PASS
>>> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-2844-9a42bdcde0f77b2c
>>> 1e947e283cc3b267b1ce2056/bat-pvc-2/igt@xe
>>> _pat@prime-external-import-coh.html> -> FAIL
>>> <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-146562v2/bat-pvc-2
>>> /igt@xe_pat@prime-external-import-coh.html>
>
next prev parent reply other threads:[~2025-03-26 17:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 21:15 [PATCH 1/2] drm/xe: Remove extra spaces in xe_vm.c Maarten Lankhorst
2025-03-20 21:15 ` [PATCH 2/2] drm/xe: Copy cpu_caching when importing DMA-BUF Maarten Lankhorst
2025-03-21 0:23 ` Matthew Brost
2025-03-21 10:23 ` Thomas Hellström
2025-03-25 8:10 ` Maarten Lankhorst
2025-03-20 21:45 ` [PATCH 1/2] drm/xe: Remove extra spaces in xe_vm.c Matthew Brost
2025-03-20 22:01 ` ✓ CI.Patch_applied: success for series starting with [1/2] " Patchwork
2025-03-20 22:01 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-20 22:02 ` ✓ CI.KUnit: success " Patchwork
2025-03-20 22:19 ` ✓ CI.Build: " Patchwork
2025-03-20 22:21 ` ✓ CI.Hooks: " Patchwork
2025-03-20 22:30 ` ✓ CI.checksparse: " Patchwork
2025-03-21 5:43 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-25 8:55 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe: Remove extra spaces in xe_vm.c (rev2) Patchwork
2025-03-25 8:55 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-25 8:56 ` ✓ CI.KUnit: success " Patchwork
2025-03-25 9:13 ` ✓ CI.Build: " Patchwork
2025-03-25 9:15 ` ✓ CI.Hooks: " Patchwork
2025-03-25 9:16 ` ✓ CI.checksparse: " Patchwork
2025-03-25 9:37 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-03-25 10:41 ` Maarten Lankhorst
2025-03-25 13:41 ` Matthew Auld
2025-03-25 19:05 ` Thomas Hellström
2025-03-26 17:51 ` Matthew Auld [this message]
2025-03-25 15:12 ` ✗ Xe.CI.Full: " Patchwork
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=f1efe4a4-0f50-43b5-b372-0cce561a8fd2@intel.com \
--to=matthew.auld@intel.com \
--cc=dev@lankhorst.se \
--cc=intel-xe@lists.freedesktop.org \
--cc=thomas.hellstrom@linux.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