From: kernel test robot <lkp@intel.com>
To: Julia Zhang <julia.zhang@amd.com>,
Gurchetan Singh <gurchetansingh@chromium.org>,
Chia-I Wu <olvaffe@gmail.com>, David Airlie <airlied@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
amd-gfx@lists.freedesktop.org,
virtualization@lists.linux-foundation.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Pierre-Eric Pelloux-Prayer" <pierre-eric.pelloux-prayer@amd.com>,
"Daniel Stone" <daniels@collabora.com>,
"Erik Faye-Lund" <kusmabite@gmail.com>,
"Marek Olšák" <marek.olsak@amd.com>,
"Chen Jiqian" <Jiqian.Chen@amd.com>,
"Huang Rui" <ray.huang@amd.com>,
"Honglei Huang" <honglei1.huang@amd.com>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Julia Zhang" <julia.zhang@amd.com>,
"Christian König" <christian.koenig@amd.com>
Subject: Re: [PATCH 1/1] drm/virtio: Implement RESOURCE_GET_LAYOUT ioctl
Date: Mon, 25 Dec 2023 08:19:56 +0800 [thread overview]
Message-ID: <202312250806.sVSnK275-lkp@intel.com> (raw)
In-Reply-To: <20231221100016.4022353-2-julia.zhang@amd.com>
Hi Julia,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.7-rc6]
[also build test WARNING on linus/master]
[cannot apply to drm-misc/drm-misc-next drm/drm-next next-20231222]
[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/Julia-Zhang/drm-virtio-Implement-RESOURCE_GET_LAYOUT-ioctl/20231222-182142
base: v6.7-rc6
patch link: https://lore.kernel.org/r/20231221100016.4022353-2-julia.zhang%40amd.com
patch subject: [PATCH 1/1] drm/virtio: Implement RESOURCE_GET_LAYOUT ioctl
config: i386-randconfig-004-20231225 (https://download.01.org/0day-ci/archive/20231225/202312250806.sVSnK275-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231225/202312250806.sVSnK275-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/202312250806.sVSnK275-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/virtio/virtgpu_ioctl.c:712:1: warning: unused label 'valid' [-Wunused-label]
valid:
^~~~~~
1 warning generated.
vim +/valid +712 drivers/gpu/drm/virtio/virtgpu_ioctl.c
673
674 static int virtio_gpu_resource_query_layout_ioctl(struct drm_device *dev,
675 void *data,
676 struct drm_file *file)
677 {
678 struct drm_virtgpu_resource_query_layout *args = data;
679 struct virtio_gpu_device *vgdev = dev->dev_private;
680 struct drm_gem_object *obj = NULL;
681 struct virtio_gpu_object *bo = NULL;
682 struct virtio_gpu_query_info bo_info = {0};
683 int ret = 0;
684 int i;
685
686 if (!vgdev->has_resource_query_layout) {
687 DRM_ERROR("failing: no RQL on host\n");
688 return -EINVAL;
689 }
690
691 if (args->handle > 0) {
692 obj = drm_gem_object_lookup(file, args->handle);
693 if (obj == NULL) {
694 DRM_ERROR("invalid handle 0x%x\n", args->handle);
695 return -ENOENT;
696 }
697 bo = gem_to_virtio_gpu_obj(obj);
698 }
699
700 ret = virtio_gpu_cmd_get_resource_layout(vgdev, &bo_info, args->width,
701 args->height, args->format,
702 args->bind, bo ? bo->hw_res_handle : 0);
703 if (ret)
704 goto out;
705
706 ret = wait_event_timeout(vgdev->resp_wq,
707 atomic_read(&bo_info.is_valid),
708 5 * HZ);
709 if (!ret)
710 goto out;
711
> 712 valid:
713 smp_rmb();
714 WARN_ON(atomic_read(&bo_info.is_valid));
715 args->num_planes = bo_info.num_planes;
716 args->modifier = bo_info.modifier;
717 for (i = 0; i < args->num_planes; i++) {
718 args->planes[i].offset = bo_info.planes[i].offset;
719 args->planes[i].stride = bo_info.planes[i].stride;
720 }
721 for (; i < VIRTIO_GPU_MAX_RESOURCE_PLANES; i++) {
722 args->planes[i].offset = 0;
723 args->planes[i].stride = 0;
724 }
725 ret = 0;
726
727 out:
728 if (obj)
729 drm_gem_object_put(obj);
730 return ret;
731 }
732
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-25 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 10:00 [PATCH v2 0/1] Implementation of resource_query_layout Julia Zhang
2023-12-21 10:00 ` [PATCH 1/1] drm/virtio: Implement RESOURCE_GET_LAYOUT ioctl Julia Zhang
2023-12-25 0:19 ` kernel test robot [this message]
2024-01-03 21:42 ` Dmitry Osipenko
2024-01-10 10:47 ` Daniel Vetter
2024-01-10 12:33 ` Zhang, Julia
[not found] ` <CAAfnVBm+oo=dnDuqp1hYVj+OrQHHp5NPUHh2oxmEVjNrsDDUTQ@mail.gmail.com>
2024-01-10 9:40 ` [PATCH v2 0/1] Implementation of resource_query_layout Zhang, Julia
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=202312250806.sVSnK275-lkp@intel.com \
--to=lkp@intel.com \
--cc=Jiqian.Chen@amd.com \
--cc=airlied@redhat.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=honglei1.huang@amd.com \
--cc=julia.zhang@amd.com \
--cc=kraxel@redhat.com \
--cc=kusmabite@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=marek.olsak@amd.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=olvaffe@gmail.com \
--cc=pierre-eric.pelloux-prayer@amd.com \
--cc=ray.huang@amd.com \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox