From: Dan Carpenter <dan.carpenter@linaro.org>
To: oe-kbuild@lists.linux.dev,
Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>,
intel-xe@lists.freedesktop.org
Cc: lkp@intel.com, oe-kbuild-all@lists.linux.dev,
Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Subject: Re: [PATCH v3 09/19] drm/xe/svm: Split system allocator vma incase of madvise call
Date: Mon, 2 Jun 2025 09:31:23 +0300 [thread overview]
Message-ID: <202505300720.uhAJlLnM-lkp@intel.com> (raw)
In-Reply-To: <20250527164003.1068118-10-himal.prasad.ghimiray@intel.com>
Hi Himal,
kernel test robot noticed the following build warnings:
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Himal-Prasad-Ghimiray/Introduce-drm_gpuvm_sm_map_ops_flags-enums-for-sm_map_ops/20250528-041919
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link: https://lore.kernel.org/r/20250527164003.1068118-10-himal.prasad.ghimiray%40intel.com
patch subject: [PATCH v3 09/19] drm/xe/svm: Split system allocator vma incase of madvise call
config: loongarch-randconfig-r073-20250529 (https://download.01.org/0day-ci/archive/20250530/202505300720.uhAJlLnM-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 15.1.0
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
| Closes: https://lore.kernel.org/r/202505300720.uhAJlLnM-lkp@intel.com/
New smatch warnings:
drivers/gpu/drm/xe/xe_vm.c:4255 xe_vm_alloc_madvise_vma() warn: variable dereferenced before check 'ops' (see line 4194)
vim +/ops +4255 drivers/gpu/drm/xe/xe_vm.c
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4175 int xe_vm_alloc_madvise_vma(struct xe_vm *vm, uint64_t start, uint64_t range)
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4176 {
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4177 struct xe_vma_ops vops;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4178 struct drm_gpuva_ops *ops = NULL;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4179 struct drm_gpuva_op *__op;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4180 bool is_cpu_addr_mirror = false;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4181 int err;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4182
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4183 vm_dbg(&vm->xe->drm, "MADVISE IN: addr=0x%016llx, size=0x%016llx", start, range);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4184
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4185 lockdep_assert_held_write(&vm->lock);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4186
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4187 vm_dbg(&vm->xe->drm, "MADVISE_OPS_CREATE: addr=0x%016llx, size=0x%016llx", start, range);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4188 ops = drm_gpuvm_sm_map_ops_create(&vm->gpuvm, start, range,
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4189 DRM_GPUVM_SKIP_GEM_OBJ_VA_SPLIT_MADVISE,
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4190 NULL, start);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4191 if (IS_ERR(ops))
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4192 return PTR_ERR(ops);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4193
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 @4194 if (list_empty(&ops->list)) {
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4195 err = 0;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4196 goto free_ops;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4197 }
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4198
[ snip ]
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4252 unwind_ops:
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4253 vm_bind_ioctl_ops_unwind(vm, &ops, 1);
^^^^
It might be nicer to change this... See below?
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4254 free_ops:
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 @4255 if (ops)
^^^^^^^^
This check is unnecessary.
If we applied this diff then it wouldn't look like maybe
vm_bind_ioctl_ops_unwind() frees ops and sets it to NULL?
diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
index 5a978da411b0..48723754b0f9 100644
--- a/drivers/gpu/drm/xe/xe_vm.c
+++ b/drivers/gpu/drm/xe/xe_vm.c
@@ -2822,13 +2822,13 @@ static void xe_vma_op_unwind(struct xe_vm *vm, struct xe_vma_op *op,
}
static void vm_bind_ioctl_ops_unwind(struct xe_vm *vm,
- struct drm_gpuva_ops **ops,
+ struct drm_gpuva_ops *ops,
int num_ops_list)
{
int i;
for (i = num_ops_list - 1; i >= 0; --i) {
- struct drm_gpuva_ops *__ops = ops[i];
+ struct drm_gpuva_ops *__ops = &ops[i];
struct drm_gpuva_op *__op;
if (!__ops)
@@ -3703,7 +3703,7 @@ int xe_vm_bind_ioctl(struct drm_device *dev, void *data, struct drm_file *file)
unwind_ops:
if (err && err != -ENODATA)
- vm_bind_ioctl_ops_unwind(vm, ops, args->num_binds);
+ vm_bind_ioctl_ops_unwind(vm, *ops, args->num_binds);
xe_vma_ops_fini(&vops);
for (i = args->num_binds - 1; i >= 0; --i)
if (ops[i])
@@ -3788,7 +3788,7 @@ struct dma_fence *xe_vm_bind_kernel_bo(struct xe_vm *vm, struct xe_bo *bo,
unwind_ops:
if (err && err != -ENODATA)
- vm_bind_ioctl_ops_unwind(vm, &ops, 1);
+ vm_bind_ioctl_ops_unwind(vm, ops, 1);
xe_vma_ops_fini(&vops);
drm_gpuva_ops_free(&vm->gpuvm, ops);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH v3 09/19] drm/xe/svm: Split system allocator vma incase of madvise call
Date: Fri, 30 May 2025 07:18:00 +0800 [thread overview]
Message-ID: <202505300720.uhAJlLnM-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20250527164003.1068118-10-himal.prasad.ghimiray@intel.com>
References: <20250527164003.1068118-10-himal.prasad.ghimiray@intel.com>
TO: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
TO: intel-xe@lists.freedesktop.org
CC: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Hi Himal,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on next-20250529]
[cannot apply to linus/master v6.15]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Himal-Prasad-Ghimiray/Introduce-drm_gpuvm_sm_map_ops_flags-enums-for-sm_map_ops/20250528-041919
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link: https://lore.kernel.org/r/20250527164003.1068118-10-himal.prasad.ghimiray%40intel.com
patch subject: [PATCH v3 09/19] drm/xe/svm: Split system allocator vma incase of madvise call
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: loongarch-randconfig-r073-20250529 (https://download.01.org/0day-ci/archive/20250530/202505300720.uhAJlLnM-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 15.1.0
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202505300720.uhAJlLnM-lkp@intel.com/
New smatch warnings:
drivers/gpu/drm/xe/xe_vm.c:4255 xe_vm_alloc_madvise_vma() warn: variable dereferenced before check 'ops' (see line 4194)
Old smatch warnings:
drivers/gpu/drm/xe/xe_vm.c:2480 new_vma() error: we previously assumed 'bo' could be null (see line 2454)
drivers/gpu/drm/xe/xe_vm.c:2492 new_vma() error: 'vma' dereferencing possible ERR_PTR()
drivers/gpu/drm/xe/xe_vm.c:2919 prefetch_ranges() warn: iterator 'i' not incremented
drivers/gpu/drm/xe/xe_vm.c:3913 xe_vm_range_tilemask_tlb_invalidation() error: uninitialized symbol 'err'.
arch/loongarch/include/asm/atomic.h:135 arch_atomic_fetch_add_unless() warn: inconsistent indenting
drivers/gpu/drm/xe/xe_vm.c:4119 xe_vm_snapshot_print() warn: passing zero to 'PTR_ERR'
vim +/ops +4255 drivers/gpu/drm/xe/xe_vm.c
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4164
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4165 /**
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4166 * xe_vm_alloc_madvise_vma - Allocate VMA's with madvise ops
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4167 * @vm: Pointer to the xe_vm structure
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4168 * @start: Starting input address
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4169 * @range: Size of the input range
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4170 *
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4171 * This function splits existing vma to create new vma for user provided input range
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4172 *
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4173 * Return: 0 if success
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4174 */
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4175 int xe_vm_alloc_madvise_vma(struct xe_vm *vm, uint64_t start, uint64_t range)
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4176 {
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4177 struct xe_vma_ops vops;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4178 struct drm_gpuva_ops *ops = NULL;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4179 struct drm_gpuva_op *__op;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4180 bool is_cpu_addr_mirror = false;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4181 int err;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4182
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4183 vm_dbg(&vm->xe->drm, "MADVISE IN: addr=0x%016llx, size=0x%016llx", start, range);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4184
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4185 lockdep_assert_held_write(&vm->lock);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4186
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4187 vm_dbg(&vm->xe->drm, "MADVISE_OPS_CREATE: addr=0x%016llx, size=0x%016llx", start, range);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4188 ops = drm_gpuvm_sm_map_ops_create(&vm->gpuvm, start, range,
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4189 DRM_GPUVM_SKIP_GEM_OBJ_VA_SPLIT_MADVISE,
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4190 NULL, start);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4191 if (IS_ERR(ops))
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4192 return PTR_ERR(ops);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4193
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 @4194 if (list_empty(&ops->list)) {
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4195 err = 0;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4196 goto free_ops;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4197 }
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4198
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4199 drm_gpuva_for_each_op(__op, ops) {
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4200 struct xe_vma_op *op = gpuva_op_to_vma_op(__op);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4201
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4202 if (__op->op == DRM_GPUVA_OP_REMAP) {
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4203 if (xe_vma_is_cpu_addr_mirror(gpuva_to_vma(op->base.remap.unmap->va)))
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4204 is_cpu_addr_mirror = true;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4205 else
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4206 is_cpu_addr_mirror = false;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4207 }
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4208
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4209 if (__op->op == DRM_GPUVA_OP_MAP)
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4210 /* In case of madvise ops DRM_GPUVA_OP_REMAP is always by
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4211 * DRM_GPUVA_OP_REMAP, so ensure we assign op->map.is_cpu_addr_mirror true
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4212 * if REMAP is for xe_vma_is_cpu_addr_mirror vma
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4213 */
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4214 op->map.is_cpu_addr_mirror = is_cpu_addr_mirror;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4215
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4216 print_op(vm->xe, __op);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4217 }
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4218
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4219 xe_vma_ops_init(&vops, vm, NULL, NULL, 0);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4220 err = vm_bind_ioctl_ops_parse(vm, ops, &vops);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4221 if (err)
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4222 goto unwind_ops;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4223
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4224 xe_vm_lock(vm, false);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4225
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4226 drm_gpuva_for_each_op(__op, ops) {
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4227 struct xe_vma_op *op = gpuva_op_to_vma_op(__op);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4228 struct xe_vma *vma;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4229 struct xe_vma_mem_attr temp_attr;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4230
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4231 if (__op->op == DRM_GPUVA_OP_UNMAP) {
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4232 /* There should be no unmap */
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4233 XE_WARN_ON("UNEXPECTED UNMAP");
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4234 xe_vma_destroy(gpuva_to_vma(op->base.unmap.va), NULL);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4235 } else if (__op->op == DRM_GPUVA_OP_REMAP) {
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4236 vma = gpuva_to_vma(op->base.remap.unmap->va);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4237 /* Store attributes for REMAP UNMAPPED VMA, so they can be assigned
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4238 * to newly MAPPED vma.
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4239 */
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4240 cp_vma_mem_attr(&temp_attr, &vma->attr);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4241 xe_vma_destroy(gpuva_to_vma(op->base.remap.unmap->va), NULL);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4242 } else if (__op->op == DRM_GPUVA_OP_MAP) {
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4243 vma = op->map.vma;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4244 cp_vma_mem_attr(&vma->attr, &temp_attr);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4245 }
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4246 }
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4247
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4248 xe_vm_unlock(vm);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4249 drm_gpuva_ops_free(&vm->gpuvm, ops);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4250 return 0;
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4251
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4252 unwind_ops:
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4253 vm_bind_ioctl_ops_unwind(vm, &ops, 1);
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 4254 free_ops:
524911c937a5a5 Himal Prasad Ghimiray 2025-05-27 @4255 if (ops)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2025-06-02 6:31 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 23:18 kernel test robot [this message]
2025-06-02 6:31 ` [PATCH v3 09/19] drm/xe/svm: Split system allocator vma incase of madvise call Dan Carpenter
-- strict thread matches above, loose matches on Subject: below --
2025-05-29 18:52 [PATCH v3 05/19] drm/xe/vma: Modify new_vma to accept struct xe_vma_mem_attr as parameter kernel test robot
2025-06-02 6:19 ` Dan Carpenter
2025-05-27 16:39 [PATCH v3 00/19] MADVISE FOR XE Himal Prasad Ghimiray
2025-05-27 16:39 ` [PATCH v3 01/19] Introduce drm_gpuvm_sm_map_ops_flags enums for sm_map_ops Himal Prasad Ghimiray
2025-05-27 16:39 ` [PATCH v3 02/19] drm/xe/uapi: Add madvise interface Himal Prasad Ghimiray
2025-05-28 16:27 ` Matthew Brost
2025-05-28 17:03 ` Souza, Jose
2025-05-29 18:03 ` Matthew Brost
2025-05-29 18:00 ` Matthew Brost
2025-06-10 4:32 ` Ghimiray, Himal Prasad
2025-05-27 16:39 ` [PATCH v3 03/19] drm/xe/vm: Add attributes struct as member of vma Himal Prasad Ghimiray
2025-05-28 16:46 ` Matthew Brost
2025-05-27 16:39 ` [PATCH v3 04/19] drm/xe/vma: Move pat_index to vma attributes Himal Prasad Ghimiray
2025-05-28 22:51 ` Matthew Brost
2025-05-27 16:39 ` [PATCH v3 05/19] drm/xe/vma: Modify new_vma to accept struct xe_vma_mem_attr as parameter Himal Prasad Ghimiray
2025-05-28 22:58 ` Matthew Brost
2025-05-27 16:39 ` [PATCH v3 06/19] drm/gpusvm: Make drm_gpusvm_for_each_* macros public Himal Prasad Ghimiray
2025-05-28 23:01 ` Matthew Brost
2025-05-27 16:39 ` [PATCH v3 07/19] drm/xe/vm: Add a helper xe_vm_range_tilemask_tlb_invalidation() Himal Prasad Ghimiray
2025-05-28 23:12 ` Matthew Brost
2025-05-29 3:21 ` Ghimiray, Himal Prasad
2025-05-27 16:39 ` [PATCH v3 08/19] drm/xe/svm: Add xe_svm_ranges_zap_ptes_in_range() for PTE zapping Himal Prasad Ghimiray
2025-05-28 23:15 ` Matthew Brost
2025-05-29 3:06 ` Ghimiray, Himal Prasad
2025-05-29 4:00 ` Matthew Brost
2025-05-30 6:29 ` Matthew Brost
2025-06-10 4:31 ` Ghimiray, Himal Prasad
2025-05-27 16:39 ` [PATCH v3 09/19] drm/xe/svm: Split system allocator vma incase of madvise call Himal Prasad Ghimiray
2025-05-29 2:49 ` Matthew Brost
2025-05-29 3:14 ` Ghimiray, Himal Prasad
2025-05-27 16:39 ` [PATCH v3 10/19] drm/xe: Implement madvise ioctl for xe Himal Prasad Ghimiray
2025-05-29 22:43 ` Matthew Brost
2025-05-30 6:36 ` Matthew Brost
2025-05-30 21:34 ` Matthew Brost
2025-06-10 4:52 ` Ghimiray, Himal Prasad
2025-06-10 5:13 ` Matthew Brost
2025-05-27 16:39 ` [PATCH v3 11/19] drm/xe: Allow CPU address mirror VMA unbind with gpu bindings for madvise Himal Prasad Ghimiray
2025-05-29 22:54 ` Matthew Brost
2025-06-12 9:02 ` Ghimiray, Himal Prasad
2025-05-27 16:39 ` [PATCH v3 12/19] drm/xe/svm : Add svm ranges migration policy on atomic access Himal Prasad Ghimiray
2025-05-29 23:27 ` Matthew Brost
2025-05-29 23:38 ` Matthew Brost
2025-05-30 4:40 ` Matthew Brost
2025-05-27 16:39 ` [PATCH v3 13/19] drm/xe/madvise: Update migration policy based on preferred location Himal Prasad Ghimiray
2025-05-29 23:42 ` Matthew Brost
2025-05-27 16:39 ` [PATCH v3 14/19] drm/xe/svm: Support DRM_XE_SVM_ATTR_PAT memory attribute Himal Prasad Ghimiray
2025-05-30 0:24 ` Matthew Brost
2025-05-27 16:39 ` [PATCH v3 15/19] drm/xe/uapi: Add flag for consulting madvise hints on svm prefetch Himal Prasad Ghimiray
2025-05-28 16:29 ` Matthew Brost
2025-05-27 16:40 ` [PATCH v3 16/19] drm/xe/svm: Consult madvise preferred location in prefetch Himal Prasad Ghimiray
2025-05-30 4:24 ` Matthew Brost
2025-06-24 18:56 ` Matthew Brost
2025-05-27 16:40 ` [PATCH v3 17/19] drm/xe/uapi: Add UAPI for querying VMA count and memory attributes Himal Prasad Ghimiray
2025-05-28 17:02 ` Souza, Jose
2025-05-30 1:11 ` kernel test robot
2025-05-30 4:29 ` Matthew Brost
2025-05-27 16:40 ` [PATCH v3 18/19] drm/xe/bo: Add attributes field to xe_bo Himal Prasad Ghimiray
2025-05-28 23:47 ` Matthew Brost
2025-05-29 2:29 ` Ghimiray, Himal Prasad
2025-05-27 16:40 ` [PATCH v3 19/19] drm/xe/bo: Update atomic_access attribute on madvise Himal Prasad Ghimiray
2025-05-28 23:46 ` Matthew Brost
2025-05-29 3:03 ` Ghimiray, Himal Prasad
2025-05-29 18:24 ` Matthew Brost
2025-05-29 18:30 ` Matthew Brost
2025-05-27 21:35 ` ✓ CI.Patch_applied: success for MADVISE FOR XE Patchwork
2025-05-27 21:35 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-27 21:37 ` ✓ CI.KUnit: success " Patchwork
2025-05-27 21:40 ` ✗ CI.Build: failure " Patchwork
2025-05-28 7:45 ` ✓ CI.Patch_applied: success " Patchwork
2025-05-28 7:45 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-28 7:46 ` ✓ CI.KUnit: success " Patchwork
2025-05-28 7:50 ` ✗ CI.Build: failure " 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=202505300720.uhAJlLnM-lkp@intel.com \
--to=dan.carpenter@linaro.org \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.