From: kernel test robot <lkp@intel.com>
To: "Huang Rui" <ray.huang@amd.com>,
dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>
Cc: Andrey Grodzovsky <andrey.grodzovsky@amd.com>,
kbuild-all@lists.01.org, amd-gfx@lists.freedesktop.org,
Huang Rui <ray.huang@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Monk Liu <Monk.Liu@amd.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v3] drm/amdgpu: introduce new amdgpu_fence object to indicate the job embedded fence
Date: Wed, 15 Dec 2021 21:30:31 +0800 [thread overview]
Message-ID: <202112152115.sqAqnvG7-lkp@intel.com> (raw)
In-Reply-To: <20211215063551.2810601-1-ray.huang@amd.com>
Hi Huang,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-intel/for-linux-next drm-tip/drm-tip v5.16-rc5 next-20211214]
[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]
url: https://github.com/0day-ci/linux/commits/Huang-Rui/drm-amdgpu-introduce-new-amdgpu_fence-object-to-indicate-the-job-embedded-fence/20211215-143731
base: git://anongit.freedesktop.org/drm/drm drm-next
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20211215/202112152115.sqAqnvG7-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/a47becf231b123760625c45242e89f5e5b5b4915
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Huang-Rui/drm-amdgpu-introduce-new-amdgpu_fence-object-to-indicate-the-job-embedded-fence/20211215-143731
git checkout a47becf231b123760625c45242e89f5e5b5b4915
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/amd/amdgpu/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:631: warning: expecting prototype for amdgpu_fence_clear_job_fences(). Prototype was for amdgpu_fence_driver_clear_job_fences() instead
vim +631 drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
623
624 /**
625 * amdgpu_fence_clear_job_fences - clear job embedded fences of ring
626 *
627 * @ring: fence of the ring to be cleared
628 *
629 */
630 void amdgpu_fence_driver_clear_job_fences(struct amdgpu_ring *ring)
> 631 {
632 int i;
633 struct dma_fence *old, **ptr;
634
635 for (i = 0; i <= ring->fence_drv.num_fences_mask; i++) {
636 ptr = &ring->fence_drv.fences[i];
637 old = rcu_dereference_protected(*ptr, 1);
638 if (old && old->ops == &amdgpu_job_fence_ops)
639 RCU_INIT_POINTER(*ptr, NULL);
640 }
641 }
642
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: "Huang Rui" <ray.huang@amd.com>,
dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>
Cc: kbuild-all@lists.01.org, amd-gfx@lists.freedesktop.org,
Huang Rui <ray.huang@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Monk Liu <Monk.Liu@amd.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v3] drm/amdgpu: introduce new amdgpu_fence object to indicate the job embedded fence
Date: Wed, 15 Dec 2021 21:30:31 +0800 [thread overview]
Message-ID: <202112152115.sqAqnvG7-lkp@intel.com> (raw)
In-Reply-To: <20211215063551.2810601-1-ray.huang@amd.com>
Hi Huang,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-intel/for-linux-next drm-tip/drm-tip v5.16-rc5 next-20211214]
[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]
url: https://github.com/0day-ci/linux/commits/Huang-Rui/drm-amdgpu-introduce-new-amdgpu_fence-object-to-indicate-the-job-embedded-fence/20211215-143731
base: git://anongit.freedesktop.org/drm/drm drm-next
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20211215/202112152115.sqAqnvG7-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/a47becf231b123760625c45242e89f5e5b5b4915
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Huang-Rui/drm-amdgpu-introduce-new-amdgpu_fence-object-to-indicate-the-job-embedded-fence/20211215-143731
git checkout a47becf231b123760625c45242e89f5e5b5b4915
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/amd/amdgpu/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:631: warning: expecting prototype for amdgpu_fence_clear_job_fences(). Prototype was for amdgpu_fence_driver_clear_job_fences() instead
vim +631 drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
623
624 /**
625 * amdgpu_fence_clear_job_fences - clear job embedded fences of ring
626 *
627 * @ring: fence of the ring to be cleared
628 *
629 */
630 void amdgpu_fence_driver_clear_job_fences(struct amdgpu_ring *ring)
> 631 {
632 int i;
633 struct dma_fence *old, **ptr;
634
635 for (i = 0; i <= ring->fence_drv.num_fences_mask; i++) {
636 ptr = &ring->fence_drv.fences[i];
637 old = rcu_dereference_protected(*ptr, 1);
638 if (old && old->ops == &amdgpu_job_fence_ops)
639 RCU_INIT_POINTER(*ptr, NULL);
640 }
641 }
642
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3] drm/amdgpu: introduce new amdgpu_fence object to indicate the job embedded fence
Date: Wed, 15 Dec 2021 21:30:31 +0800 [thread overview]
Message-ID: <202112152115.sqAqnvG7-lkp@intel.com> (raw)
In-Reply-To: <20211215063551.2810601-1-ray.huang@amd.com>
[-- Attachment #1: Type: text/plain, Size: 2479 bytes --]
Hi Huang,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-intel/for-linux-next drm-tip/drm-tip v5.16-rc5 next-20211214]
[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]
url: https://github.com/0day-ci/linux/commits/Huang-Rui/drm-amdgpu-introduce-new-amdgpu_fence-object-to-indicate-the-job-embedded-fence/20211215-143731
base: git://anongit.freedesktop.org/drm/drm drm-next
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20211215/202112152115.sqAqnvG7-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/a47becf231b123760625c45242e89f5e5b5b4915
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Huang-Rui/drm-amdgpu-introduce-new-amdgpu_fence-object-to-indicate-the-job-embedded-fence/20211215-143731
git checkout a47becf231b123760625c45242e89f5e5b5b4915
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/amd/amdgpu/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:631: warning: expecting prototype for amdgpu_fence_clear_job_fences(). Prototype was for amdgpu_fence_driver_clear_job_fences() instead
vim +631 drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
623
624 /**
625 * amdgpu_fence_clear_job_fences - clear job embedded fences of ring
626 *
627 * @ring: fence of the ring to be cleared
628 *
629 */
630 void amdgpu_fence_driver_clear_job_fences(struct amdgpu_ring *ring)
> 631 {
632 int i;
633 struct dma_fence *old, **ptr;
634
635 for (i = 0; i <= ring->fence_drv.num_fences_mask; i++) {
636 ptr = &ring->fence_drv.fences[i];
637 old = rcu_dereference_protected(*ptr, 1);
638 if (old && old->ops == &amdgpu_job_fence_ops)
639 RCU_INIT_POINTER(*ptr, NULL);
640 }
641 }
642
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: "Huang Rui" <ray.huang@amd.com>,
dri-devel@lists.freedesktop.org,
"Christian König" <christian.koenig@amd.com>,
"Daniel Vetter" <daniel.vetter@ffwll.ch>,
"Sumit Semwal" <sumit.semwal@linaro.org>
Cc: kbuild-all@lists.01.org, amd-gfx@lists.freedesktop.org,
linux-media@vger.kernel.org,
Alex Deucher <alexander.deucher@amd.com>,
Monk Liu <Monk.Liu@amd.com>,
Andrey Grodzovsky <andrey.grodzovsky@amd.com>,
Huang Rui <ray.huang@amd.com>
Subject: Re: [PATCH v3] drm/amdgpu: introduce new amdgpu_fence object to indicate the job embedded fence
Date: Wed, 15 Dec 2021 21:30:31 +0800 [thread overview]
Message-ID: <202112152115.sqAqnvG7-lkp@intel.com> (raw)
In-Reply-To: <20211215063551.2810601-1-ray.huang@amd.com>
Hi Huang,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on drm-intel/for-linux-next drm-tip/drm-tip v5.16-rc5 next-20211214]
[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]
url: https://github.com/0day-ci/linux/commits/Huang-Rui/drm-amdgpu-introduce-new-amdgpu_fence-object-to-indicate-the-job-embedded-fence/20211215-143731
base: git://anongit.freedesktop.org/drm/drm drm-next
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20211215/202112152115.sqAqnvG7-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/0day-ci/linux/commit/a47becf231b123760625c45242e89f5e5b5b4915
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Huang-Rui/drm-amdgpu-introduce-new-amdgpu_fence-object-to-indicate-the-job-embedded-fence/20211215-143731
git checkout a47becf231b123760625c45242e89f5e5b5b4915
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/amd/amdgpu/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:631: warning: expecting prototype for amdgpu_fence_clear_job_fences(). Prototype was for amdgpu_fence_driver_clear_job_fences() instead
vim +631 drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c
623
624 /**
625 * amdgpu_fence_clear_job_fences - clear job embedded fences of ring
626 *
627 * @ring: fence of the ring to be cleared
628 *
629 */
630 void amdgpu_fence_driver_clear_job_fences(struct amdgpu_ring *ring)
> 631 {
632 int i;
633 struct dma_fence *old, **ptr;
634
635 for (i = 0; i <= ring->fence_drv.num_fences_mask; i++) {
636 ptr = &ring->fence_drv.fences[i];
637 old = rcu_dereference_protected(*ptr, 1);
638 if (old && old->ops == &amdgpu_job_fence_ops)
639 RCU_INIT_POINTER(*ptr, NULL);
640 }
641 }
642
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
next prev parent reply other threads:[~2021-12-15 13:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 6:35 [PATCH v3] drm/amdgpu: introduce new amdgpu_fence object to indicate the job embedded fence Huang Rui
2021-12-15 6:35 ` Huang Rui
2021-12-15 6:35 ` Huang Rui
2021-12-15 10:57 ` Christian König
2021-12-15 10:57 ` Christian König
2021-12-15 10:57 ` Christian König
2021-12-15 13:30 ` kernel test robot [this message]
2021-12-15 13:30 ` kernel test robot
2021-12-15 13:30 ` kernel test robot
2021-12-15 13:30 ` kernel test robot
2021-12-16 4:34 ` Huang Rui
2021-12-16 4:34 ` Huang Rui
2021-12-16 4:34 ` Huang Rui
2021-12-16 4:34 ` Huang Rui
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=202112152115.sqAqnvG7-lkp@intel.com \
--to=lkp@intel.com \
--cc=Monk.Liu@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrey.grodzovsky@amd.com \
--cc=christian.koenig@amd.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-media@vger.kernel.org \
--cc=ray.huang@amd.com \
--cc=sumit.semwal@linaro.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 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.