[agd5f:kq_resets 16/41] drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:742: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



tree:   https://gitlab.freedesktop.org/agd5f/linux.git kq_resets
head:   524eebfdd4b30fd63ca774d7ea346bcf0e8e76b1
commit: 2ed8b69e9971cd99c0fed42c9e0ecf24d3d2b481 [16/41] drm/amdgpu: track ring state associated with a fence
config: x86_64-rhel-9.4-rust (https://download.01.org/0day-ci/archive/20250724/202507241307.3zdfZT68-lkp@xxxxxxxxx/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
rustc: rustc 1.88.0 (6b00bc388 2025-06-23)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250724/202507241307.3zdfZT68-lkp@xxxxxxxxx/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@xxxxxxxxx>
| Closes: https://lore.kernel.org/oe-kbuild-all/202507241307.3zdfZT68-lkp@xxxxxxxxx/

All warnings (new ones prefixed by >>):

>> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:742: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
    * Kernel queue reset handling


vim +742 drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c

   739	
   740	
   741	/**
 > 742	 * Kernel queue reset handling
   743	 *
   744	 * The driver can reset individual queues for most engines, but those queues
   745	 * may contain work from multiple contexts.  Resetting the queue will reset
   746	 * lose all of that state.  In order to minimize the collateral damage, the
   747	 * driver will save the ring contents which are not associated with the guilty
   748	 * context prior to resetting the queue.  After resetting the queue the queue
   749	 * contents from the other contexts is re-emitted to the rings so that it can
   750	 * be processed by the engine.  To handle this, we save the queue's write
   751	 * pointer (wptr) in the fences associated with each context.  If we get a
   752	 * queue timeout, we can then use the wptrs from the fences to determine
   753	 * which data needs to be saved out of the queue's ring buffer.
   754	 */
   755	

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




[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux