From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Arvind Yadav" <arvind.yadav@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.checkpatch: warning for drm/xe/svm: Add MMU notifier-based madvise autoreset on munmap (rev2)
Date: Mon, 06 Apr 2026 09:04:10 -0000 [thread overview]
Message-ID: <177546625091.433781.7079221935220788006@a3b018990fe9> (raw)
In-Reply-To: <20260406085830.1118431-1-arvind.yadav@intel.com>
== Series Details ==
Series: drm/xe/svm: Add MMU notifier-based madvise autoreset on munmap (rev2)
URL : https://patchwork.freedesktop.org/series/161815/
State : warning
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
1f57ba1afceae32108bd24770069f764d940a0e4
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 30a917b2848a008b15b633df7972f0d102ef3b7f
Author: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Date: Mon Apr 6 14:28:30 2026 +0530
drm/xe/svm: Correct memory attribute reset for partial unmap
When performing a partial unmap of an SVM range, the memory attributes
were being reset for the entire range instead of just the portion
being unmapped. This could lead to unintended side effects and behaviour.
Fix this by restricting the attribute reset to only the affected subrange
that is being unmapped.
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: Thomas Hellström <thomas.hellstrom@linux.intel.com>
Signed-off-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Signed-off-by: Arvind Yadav <arvind.yadav@intel.com>
+ /mt/dim checkpatch d873f0156bd08a3031097d459e2d3604bfe1b1bf drm-intel
e7c4c655a87f drm/xe/vm: Track CPU_AUTORESET state in xe_vma
7553903d21cb drm/xe/vm: Preserve cpu_autoreset_active across GPUVA operations
43d48b4dbc79 drm/xe/svm: Clear CPU_AUTORESET_ACTIVE on first GPU fault
06d48e6a6d2a drm/xe/vm: Add madvise autoreset interval notifier worker infrastructure
c542fcf2f0ad drm/xe/vm: Deactivate madvise notifier on GPU touch
-:121: CHECK:PARENTHESIS_ALIGNMENT: Alignment should match open parenthesis
#121: FILE: drivers/gpu/drm/xe/xe_vm_madvise.c:1268:
+ xe_vm_deactivate_madvise_notifier_for_range(vm,
+ xe_vma_start(vma),
total: 0 errors, 0 warnings, 1 checks, 106 lines checked
e2c77b8c3bf2 drm/xe/vm: Wire MADVISE_AUTORESET notifiers into VM lifecycle
30a917b2848a drm/xe/svm: Correct memory attribute reset for partial unmap
next prev parent reply other threads:[~2026-04-06 9:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-06 8:58 [RFC v2 0/7] drm/xe/svm: Add MMU notifier-based madvise autoreset on munmap Arvind Yadav
2026-04-06 8:58 ` [RFC v2 1/7] drm/xe/vm: Track CPU_AUTORESET state in xe_vma Arvind Yadav
2026-04-30 4:07 ` Matthew Brost
2026-06-04 5:31 ` Yadav, Arvind
2026-04-06 8:58 ` [RFC v2 2/7] drm/xe/vm: Preserve cpu_autoreset_active across GPUVA operations Arvind Yadav
2026-04-30 4:29 ` Matthew Brost
2026-06-04 5:40 ` Yadav, Arvind
2026-04-06 8:58 ` [RFC v2 3/7] drm/xe/svm: Clear CPU_AUTORESET_ACTIVE on first GPU fault Arvind Yadav
2026-04-30 4:26 ` Matthew Brost
2026-06-04 5:38 ` Yadav, Arvind
2026-04-06 8:58 ` [RFC v2 4/7] drm/xe/vm: Add madvise autoreset interval notifier worker infrastructure Arvind Yadav
2026-04-06 8:58 ` [RFC v2 5/7] drm/xe/vm: Deactivate madvise notifier on GPU touch Arvind Yadav
2026-04-06 8:58 ` [RFC v2 6/7] drm/xe/vm: Wire MADVISE_AUTORESET notifiers into VM lifecycle Arvind Yadav
2026-04-06 8:58 ` [RFC v2 7/7] drm/xe/svm: Correct memory attribute reset for partial unmap Arvind Yadav
2026-04-30 5:02 ` Matthew Brost
2026-04-30 5:08 ` Matthew Brost
2026-06-04 6:05 ` Yadav, Arvind
2026-04-06 9:04 ` Patchwork [this message]
2026-04-06 9:06 ` ✓ CI.KUnit: success for drm/xe/svm: Add MMU notifier-based madvise autoreset on munmap (rev2) Patchwork
2026-04-06 9:54 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-06 12:36 ` ✓ 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=177546625091.433781.7079221935220788006@a3b018990fe9 \
--to=patchwork@emeril.freedesktop.org \
--cc=arvind.yadav@intel.com \
--cc=intel-xe@lists.freedesktop.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 read-only IMAP folder(s) and NNTP newsgroup(s).