All of lore.kernel.org
 help / color / mirror / Atom feed
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 v4 04/28] drm/xe/pf: Add save/restore control state stubs and connect to debugfs
Date: Thu, 6 Nov 2025 07:08:45 +0800	[thread overview]
Message-ID: <202511060745.V5s5AlIB-lkp@intel.com> (raw)

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20251105151027.540712-5-michal.winiarski@intel.com>
References: <20251105151027.540712-5-michal.winiarski@intel.com>
TO: "Michał Winiarski" <michal.winiarski@intel.com>
TO: Alex Williamson <alex@shazbot.org>
TO: Lucas De Marchi <lucas.demarchi@intel.com>
TO: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
TO: Rodrigo Vivi <rodrigo.vivi@intel.com>
TO: Jason Gunthorpe <jgg@ziepe.ca>
TO: Yishai Hadas <yishaih@nvidia.com>
TO: Kevin Tian <kevin.tian@intel.com>
TO: Shameer Kolothum <skolothumtho@nvidia.com>
TO: intel-xe@lists.freedesktop.org
TO: linux-kernel@vger.kernel.org
TO: kvm@vger.kernel.org
TO: Matthew Brost <matthew.brost@intel.com>
TO: Michal Wajdeczko <michal.wajdeczko@intel.com>
CC: dri-devel@lists.freedesktop.org
CC: Jani Nikula <jani.nikula@linux.intel.com>
CC: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
CC: Tvrtko Ursulin <tursulin@ursulin.net>
CC: David Airlie <airlied@gmail.com>
CC: Simona Vetter <simona@ffwll.ch>
CC: Lukasz Laguna <lukasz.laguna@intel.com>
CC: Christoph Hellwig <hch@infradead.org>
CC: "Michał Winiarski" <michal.winiarski@intel.com>

Hi Michał,

kernel test robot noticed the following build warnings:

[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on next-20251105]
[cannot apply to awilliam-vfio/next awilliam-vfio/for-linus drm-i915/for-linux-next drm-i915/for-linux-next-fixes linus/master v6.18-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/Micha-Winiarski/drm-xe-pf-Remove-GuC-version-check-for-migration-support/20251105-234203
base:   https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link:    https://lore.kernel.org/r/20251105151027.540712-5-michal.winiarski%40intel.com
patch subject: [PATCH v4 04/28] drm/xe/pf: Add save/restore control state stubs and connect to debugfs
:::::: branch date: 7 hours ago
:::::: commit date: 7 hours ago
config: alpha-randconfig-r072-20251106 (https://download.01.org/0day-ci/archive/20251106/202511060745.V5s5AlIB-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 8.5.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/202511060745.V5s5AlIB-lkp@intel.com/

smatch warnings:
drivers/gpu/drm/xe/xe_sriov_pf_control.c:198 xe_sriov_pf_control_finish_save_vf() error: uninitialized symbol 'ret'.
drivers/gpu/drm/xe/xe_sriov_pf_control.c:222 xe_sriov_pf_control_trigger_restore_vf() error: uninitialized symbol 'ret'.
drivers/gpu/drm/xe/xe_sriov_pf_control.c:246 xe_sriov_pf_control_finish_restore_vf() error: uninitialized symbol 'ret'.

vim +/ret +198 drivers/gpu/drm/xe/xe_sriov_pf_control.c

33b59ab90959e2 Michał Winiarski 2025-11-05  176  
33b59ab90959e2 Michał Winiarski 2025-11-05  177  /**
33b59ab90959e2 Michał Winiarski 2025-11-05  178   * xe_sriov_pf_control_finish_save_vf - Complete a VF migration data SAVE sequence on all GTs.
33b59ab90959e2 Michał Winiarski 2025-11-05  179   * @xe: the &xe_device
33b59ab90959e2 Michał Winiarski 2025-11-05  180   * @vfid: the VF identifier
33b59ab90959e2 Michał Winiarski 2025-11-05  181   *
33b59ab90959e2 Michał Winiarski 2025-11-05  182   * This function is for PF only.
33b59ab90959e2 Michał Winiarski 2025-11-05  183   *
33b59ab90959e2 Michał Winiarski 2025-11-05  184   * Return: 0 on success or a negative error code on failure.
33b59ab90959e2 Michał Winiarski 2025-11-05  185   */
33b59ab90959e2 Michał Winiarski 2025-11-05  186  int xe_sriov_pf_control_finish_save_vf(struct xe_device *xe, unsigned int vfid)
33b59ab90959e2 Michał Winiarski 2025-11-05  187  {
33b59ab90959e2 Michał Winiarski 2025-11-05  188  	struct xe_gt *gt;
33b59ab90959e2 Michał Winiarski 2025-11-05  189  	unsigned int id;
33b59ab90959e2 Michał Winiarski 2025-11-05  190  	int ret;
33b59ab90959e2 Michał Winiarski 2025-11-05  191  
33b59ab90959e2 Michał Winiarski 2025-11-05  192  	for_each_gt(gt, xe, id) {
33b59ab90959e2 Michał Winiarski 2025-11-05  193  		ret = xe_gt_sriov_pf_control_finish_save_vf(gt, vfid);
33b59ab90959e2 Michał Winiarski 2025-11-05  194  		if (ret)
33b59ab90959e2 Michał Winiarski 2025-11-05  195  			break;
33b59ab90959e2 Michał Winiarski 2025-11-05  196  	}
33b59ab90959e2 Michał Winiarski 2025-11-05  197  
33b59ab90959e2 Michał Winiarski 2025-11-05 @198  	return ret;
33b59ab90959e2 Michał Winiarski 2025-11-05  199  }
33b59ab90959e2 Michał Winiarski 2025-11-05  200  
33b59ab90959e2 Michał Winiarski 2025-11-05  201  /**
33b59ab90959e2 Michał Winiarski 2025-11-05  202   * xe_sriov_pf_control_trigger_restore_vf - Start a VF migration data RESTORE sequence on all GTs.
33b59ab90959e2 Michał Winiarski 2025-11-05  203   * @xe: the &xe_device
33b59ab90959e2 Michał Winiarski 2025-11-05  204   * @vfid: the VF identifier
33b59ab90959e2 Michał Winiarski 2025-11-05  205   *
33b59ab90959e2 Michał Winiarski 2025-11-05  206   * This function is for PF only.
33b59ab90959e2 Michał Winiarski 2025-11-05  207   *
33b59ab90959e2 Michał Winiarski 2025-11-05  208   * Return: 0 on success or a negative error code on failure.
33b59ab90959e2 Michał Winiarski 2025-11-05  209   */
33b59ab90959e2 Michał Winiarski 2025-11-05  210  int xe_sriov_pf_control_trigger_restore_vf(struct xe_device *xe, unsigned int vfid)
33b59ab90959e2 Michał Winiarski 2025-11-05  211  {
33b59ab90959e2 Michał Winiarski 2025-11-05  212  	struct xe_gt *gt;
33b59ab90959e2 Michał Winiarski 2025-11-05  213  	unsigned int id;
33b59ab90959e2 Michał Winiarski 2025-11-05  214  	int ret;
33b59ab90959e2 Michał Winiarski 2025-11-05  215  
33b59ab90959e2 Michał Winiarski 2025-11-05  216  	for_each_gt(gt, xe, id) {
33b59ab90959e2 Michał Winiarski 2025-11-05  217  		ret = xe_gt_sriov_pf_control_trigger_restore_vf(gt, vfid);
33b59ab90959e2 Michał Winiarski 2025-11-05  218  		if (ret)
33b59ab90959e2 Michał Winiarski 2025-11-05  219  			return ret;
33b59ab90959e2 Michał Winiarski 2025-11-05  220  	}
33b59ab90959e2 Michał Winiarski 2025-11-05  221  
33b59ab90959e2 Michał Winiarski 2025-11-05 @222  	return ret;
33b59ab90959e2 Michał Winiarski 2025-11-05  223  }
33b59ab90959e2 Michał Winiarski 2025-11-05  224  
33b59ab90959e2 Michał Winiarski 2025-11-05  225  /**
33b59ab90959e2 Michał Winiarski 2025-11-05  226   * xe_sriov_pf_control_wait_restore_vf - Complete a VF migration data RESTORE sequence in all GTs.
33b59ab90959e2 Michał Winiarski 2025-11-05  227   * @xe: the &xe_device
33b59ab90959e2 Michał Winiarski 2025-11-05  228   * @vfid: the VF identifier
33b59ab90959e2 Michał Winiarski 2025-11-05  229   *
33b59ab90959e2 Michał Winiarski 2025-11-05  230   * This function is for PF only.
33b59ab90959e2 Michał Winiarski 2025-11-05  231   *
33b59ab90959e2 Michał Winiarski 2025-11-05  232   * Return: 0 on success or a negative error code on failure.
33b59ab90959e2 Michał Winiarski 2025-11-05  233   */
33b59ab90959e2 Michał Winiarski 2025-11-05  234  int xe_sriov_pf_control_finish_restore_vf(struct xe_device *xe, unsigned int vfid)
33b59ab90959e2 Michał Winiarski 2025-11-05  235  {
33b59ab90959e2 Michał Winiarski 2025-11-05  236  	struct xe_gt *gt;
33b59ab90959e2 Michał Winiarski 2025-11-05  237  	unsigned int id;
33b59ab90959e2 Michał Winiarski 2025-11-05  238  	int ret;
33b59ab90959e2 Michał Winiarski 2025-11-05  239  
33b59ab90959e2 Michał Winiarski 2025-11-05  240  	for_each_gt(gt, xe, id) {
33b59ab90959e2 Michał Winiarski 2025-11-05  241  		ret = xe_gt_sriov_pf_control_finish_restore_vf(gt, vfid);
33b59ab90959e2 Michał Winiarski 2025-11-05  242  		if (ret)
33b59ab90959e2 Michał Winiarski 2025-11-05  243  			break;
33b59ab90959e2 Michał Winiarski 2025-11-05  244  	}
33b59ab90959e2 Michał Winiarski 2025-11-05  245  
33b59ab90959e2 Michał Winiarski 2025-11-05 @246  	return ret;

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

             reply	other threads:[~2025-11-05 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 23:08 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-05 15:09 [PATCH v4 00/28] vfio/xe: Add driver variant for Xe VF migration Michał Winiarski
2025-11-05 15:10 ` [PATCH v4 04/28] drm/xe/pf: Add save/restore control state stubs and connect to debugfs Michał Winiarski

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=202511060745.V5s5AlIB-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=error27@gmail.com \
    --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.