Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jonathan Cavitt <jonathan.cavitt@intel.com>,
	intel-xe@lists.freedesktop.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	saurabhg.gupta@intel.com, alex.zuo@intel.com,
	jonathan.cavitt@intel.com, joonas.lahtinen@linux.intel.com,
	matthew.brost@intel.com, jianxun.zhang@intel.com,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 8/8] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl
Date: Fri, 28 Feb 2025 11:44:03 +0800	[thread overview]
Message-ID: <202502281118.XNrfLzlo-lkp@intel.com> (raw)
In-Reply-To: <20250227191457.84035-9-jonathan.cavitt@intel.com>

Hi Jonathan,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on next-20250227]
[cannot apply to linus/master v6.14-rc4]
[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/Jonathan-Cavitt/drm-xe-xe_gt_pagefault-Disallow-writes-to-read-only-VMAs/20250228-032204
base:   https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link:    https://lore.kernel.org/r/20250227191457.84035-9-jonathan.cavitt%40intel.com
patch subject: [PATCH v2 8/8] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl
config: i386-buildonly-randconfig-002-20250228 (https://download.01.org/0day-ci/archive/20250228/202502281118.XNrfLzlo-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250228/202502281118.XNrfLzlo-lkp@intel.com/reproduce)

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>
| Closes: https://lore.kernel.org/oe-kbuild-all/202502281118.XNrfLzlo-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/xe/xe_vm.c:3267:3: warning: label followed by a declaration is a C23 extension [-Wc23-extensions]
    3267 |                 struct xe_exec_queue_ban_entry *entry;
         |                 ^
   1 warning generated.


vim +3267 drivers/gpu/drm/xe/xe_vm.c

  3260	
  3261	static u32 xe_vm_get_property_size(struct xe_vm *vm, u32 property)
  3262	{
  3263		u32 size = 0;
  3264	
  3265		switch (property) {
  3266		case DRM_XE_VM_GET_PROPERTY_FAULTS:
> 3267			struct xe_exec_queue_ban_entry *entry;
  3268	
  3269			spin_lock(&vm->bans.lock);
  3270			list_for_each_entry(entry, &vm->bans.list, list) {
  3271				struct xe_pagefault *pf = entry->pf;
  3272	
  3273				size += pf ? sizeof(struct drm_xe_ban) : 0;
  3274			}
  3275			spin_unlock(&vm->bans.lock);
  3276			return size;
  3277		case DRM_XE_VM_GET_PROPERTY_BANS:
  3278			spin_lock(&vm->bans.lock);
  3279			size = vm->bans.len * sizeof(struct drm_xe_ban);
  3280			spin_unlock(&vm->bans.lock);
  3281			return size;
  3282		case DRM_XE_VM_GET_PROPERTY_NUM_RESETS:
  3283			return 0;
  3284		default:
  3285			return -EINVAL;
  3286		}
  3287	}
  3288	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2025-02-28  3:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 19:14 [PATCH v2 0/8] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 1/8] drm/xe/xe_gt_pagefault: Disallow writes to read-only VMAs Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 2/8] drm/xe/xe_exec_queue: Add ID param to exec queue struct Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 3/8] drm/xe/xe_gt_pagefault: Migrate pagefault struct to header Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 4/8] drm/xe/xe_vm: Add per VM pagefault info Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 5/8] drm/xe/xe_vm: Add per VM reset stats Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 6/8] drm/xe/uapi: Define drm_xe_vm_get_property Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 7/8] drm/xe/xe_gt_pagefault: Add address_type field to pagefaults Jonathan Cavitt
2025-02-27 19:14 ` [PATCH v2 8/8] drm/xe/xe_vm: Implement xe_vm_get_property_ioctl Jonathan Cavitt
2025-02-28  3:44   ` kernel test robot [this message]
2025-02-27 21:01 ` ✓ CI.Patch_applied: success for drm/xe/xe_vm: Implement xe_vm_get_property_ioctl (rev2) Patchwork
2025-02-27 21:01 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-27 21:02 ` ✓ CI.KUnit: success " Patchwork
2025-02-27 21:19 ` ✓ CI.Build: " Patchwork
2025-02-27 21:21 ` ✓ CI.Hooks: " Patchwork
2025-02-27 21:23 ` ✓ CI.checksparse: " Patchwork
2025-02-27 21:43 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-02-28  2:08 ` ✗ 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=202502281118.XNrfLzlo-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alex.zuo@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jianxun.zhang@intel.com \
    --cc=jonathan.cavitt@intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=llvm@lists.linux.dev \
    --cc=matthew.brost@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=saurabhg.gupta@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