From: kernel test robot <lkp@intel.com>
To: Viktor Prutyanov <viktor@daynix.com>,
mst@redhat.com, jasowang@redhat.com
Cc: oe-kbuild-all@lists.linux.dev,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, yan@daynix.com, viktor@daynix.com
Subject: Re: [PATCH] virtio: add VIRTIO_F_NOTIFICATION_DATA feature support
Date: Tue, 21 Mar 2023 04:35:00 +0800 [thread overview]
Message-ID: <202303210403.LsRG8goQ-lkp@intel.com> (raw)
In-Reply-To: <20230320115451.1232171-1-viktor@daynix.com>
Hi Viktor,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on mst-vhost/linux-next]
[also build test WARNING on linus/master v6.3-rc3 next-20230320]
[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/Viktor-Prutyanov/virtio-add-VIRTIO_F_NOTIFICATION_DATA-feature-support/20230320-195725
base: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
patch link: https://lore.kernel.org/r/20230320115451.1232171-1-viktor%40daynix.com
patch subject: [PATCH] virtio: add VIRTIO_F_NOTIFICATION_DATA feature support
config: i386-randconfig-s003 (https://download.01.org/0day-ci/archive/20230321/202303210403.LsRG8goQ-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://github.com/intel-lab-lkp/linux/commit/b6212a12ca1691dc346e5de046ec46bd3ce11247
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Viktor-Prutyanov/virtio-add-VIRTIO_F_NOTIFICATION_DATA-feature-support/20230320-195725
git checkout b6212a12ca1691dc346e5de046ec46bd3ce11247
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 olddefconfig
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/virtio/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303210403.LsRG8goQ-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/virtio/virtio_mmio.c:293:16: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected unsigned int val @@ got restricted __le32 [usertype] data @@
drivers/virtio/virtio_mmio.c:293:16: sparse: expected unsigned int val
drivers/virtio/virtio_mmio.c:293:16: sparse: got restricted __le32 [usertype] data
vim +293 drivers/virtio/virtio_mmio.c
287
288 static bool vm_notify_with_data(struct virtqueue *vq)
289 {
290 struct virtio_mmio_device *vm_dev = to_virtio_mmio_device(vq->vdev);
291 __le32 data = vring_fill_notification_data(vq);
292
> 293 writel(data, vm_dev->base + VIRTIO_MMIO_QUEUE_NOTIFY);
294
295 return true;
296 }
297
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Viktor Prutyanov <viktor@daynix.com>,
mst@redhat.com, jasowang@redhat.com
Cc: yan@daynix.com, virtualization@lists.linux-foundation.org,
viktor@daynix.com, linux-kernel@vger.kernel.org,
oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH] virtio: add VIRTIO_F_NOTIFICATION_DATA feature support
Date: Tue, 21 Mar 2023 04:35:00 +0800 [thread overview]
Message-ID: <202303210403.LsRG8goQ-lkp@intel.com> (raw)
In-Reply-To: <20230320115451.1232171-1-viktor@daynix.com>
Hi Viktor,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on mst-vhost/linux-next]
[also build test WARNING on linus/master v6.3-rc3 next-20230320]
[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/Viktor-Prutyanov/virtio-add-VIRTIO_F_NOTIFICATION_DATA-feature-support/20230320-195725
base: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next
patch link: https://lore.kernel.org/r/20230320115451.1232171-1-viktor%40daynix.com
patch subject: [PATCH] virtio: add VIRTIO_F_NOTIFICATION_DATA feature support
config: i386-randconfig-s003 (https://download.01.org/0day-ci/archive/20230321/202303210403.LsRG8goQ-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://github.com/intel-lab-lkp/linux/commit/b6212a12ca1691dc346e5de046ec46bd3ce11247
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Viktor-Prutyanov/virtio-add-VIRTIO_F_NOTIFICATION_DATA-feature-support/20230320-195725
git checkout b6212a12ca1691dc346e5de046ec46bd3ce11247
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 olddefconfig
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=i386 SHELL=/bin/bash drivers/virtio/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303210403.LsRG8goQ-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/virtio/virtio_mmio.c:293:16: sparse: sparse: incorrect type in argument 1 (different base types) @@ expected unsigned int val @@ got restricted __le32 [usertype] data @@
drivers/virtio/virtio_mmio.c:293:16: sparse: expected unsigned int val
drivers/virtio/virtio_mmio.c:293:16: sparse: got restricted __le32 [usertype] data
vim +293 drivers/virtio/virtio_mmio.c
287
288 static bool vm_notify_with_data(struct virtqueue *vq)
289 {
290 struct virtio_mmio_device *vm_dev = to_virtio_mmio_device(vq->vdev);
291 __le32 data = vring_fill_notification_data(vq);
292
> 293 writel(data, vm_dev->base + VIRTIO_MMIO_QUEUE_NOTIFY);
294
295 return true;
296 }
297
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2023-03-20 20:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 11:54 [PATCH] virtio: add VIRTIO_F_NOTIFICATION_DATA feature support Viktor Prutyanov
2023-03-20 17:25 ` Michael S. Tsirkin
2023-03-20 17:25 ` Michael S. Tsirkin
2023-03-20 20:34 ` kernel test robot
2023-03-20 20:34 ` kernel test robot
2023-03-20 20:35 ` kernel test robot [this message]
2023-03-20 20:35 ` kernel test robot
2023-03-20 20:55 ` kernel test robot
2023-03-20 20:55 ` kernel test robot
2023-03-20 21:06 ` kernel test robot
2023-03-20 21:06 ` kernel test robot
2023-03-20 21:58 ` kernel test robot
2023-03-20 21:58 ` kernel test robot
2023-03-20 23:30 ` kernel test robot
2023-03-20 23:30 ` kernel test robot
2023-03-21 0:11 ` kernel test robot
2023-03-21 0:11 ` kernel test robot
2023-03-21 2:15 ` Xuan Zhuo
2023-03-21 2:15 ` Xuan Zhuo
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=202303210403.LsRG8goQ-lkp@intel.com \
--to=lkp@intel.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=viktor@daynix.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=yan@daynix.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 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.