From: kernel test robot <lkp@intel.com>
To: Grzegorz Jaszczyk <jaz@semihalf.com>,
linux-kernel@vger.kernel.org, alex.williamson@redhat.com
Cc: oe-kbuild-all@lists.linux.dev, dmy@semihalf.com, tn@semihalf.com,
dbehr@google.com, dbehr@chromium.org, upstream@semihalf.com,
dtor@google.com, jgg@ziepe.ca, kevin.tian@intel.com,
cohuck@redhat.com, abhsahu@nvidia.com, yishaih@nvidia.com,
yi.l.liu@intel.com, kvm@vger.kernel.org, libvir-list@redhat.com,
Grzegorz Jaszczyk <jaz@semihalf.com>
Subject: Re: [PATCH v2] vfio/pci: Propagate ACPI notifications to user-space via eventfd
Date: Tue, 25 Apr 2023 03:11:13 +0800 [thread overview]
Message-ID: <202304250252.8MirvFb0-lkp@intel.com> (raw)
In-Reply-To: <20230424162748.2711945-1-jaz@semihalf.com>
Hi Grzegorz,
kernel test robot noticed the following build warnings:
[auto build test WARNING on awilliam-vfio/for-linus]
[also build test WARNING on linus/master v6.3 next-20230421]
[cannot apply to awilliam-vfio/next]
[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/Grzegorz-Jaszczyk/vfio-pci-Propagate-ACPI-notifications-to-user-space-via-eventfd/20230425-002935
base: https://github.com/awilliam/linux-vfio.git for-linus
patch link: https://lore.kernel.org/r/20230424162748.2711945-1-jaz%40semihalf.com
patch subject: [PATCH v2] vfio/pci: Propagate ACPI notifications to user-space via eventfd
config: ia64-allmodconfig (https://download.01.org/0day-ci/archive/20230425/202304250252.8MirvFb0-lkp@intel.com/config)
compiler: ia64-linux-gcc (GCC) 12.1.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/62d759059cd5e6dab70052027e1b69c5d5cdc0f2
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Grzegorz-Jaszczyk/vfio-pci-Propagate-ACPI-notifications-to-user-space-via-eventfd/20230425-002935
git checkout 62d759059cd5e6dab70052027e1b69c5d5cdc0f2
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=ia64 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=ia64 SHELL=/bin/bash drivers/vfio/pci/
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/202304250252.8MirvFb0-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/vfio/pci/vfio_pci_core.c:709:6: warning: no previous prototype for 'vfio_pci_acpi_notify_close_device' [-Wmissing-prototypes]
709 | void vfio_pci_acpi_notify_close_device(struct vfio_pci_core_device *vdev)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/vfio/pci/vfio_pci_core.c: In function 'vfio_pci_ioctl_acpi_notify_eventfd':
>> drivers/vfio/pci/vfio_pci_core.c:1029:18: warning: variable 'events' set but not used [-Wunused-but-set-variable]
1029 | __poll_t events;
| ^~~~~~
vim +/vfio_pci_acpi_notify_close_device +709 drivers/vfio/pci/vfio_pci_core.c
708
> 709 void vfio_pci_acpi_notify_close_device(struct vfio_pci_core_device *vdev)
710 {
711 struct vfio_acpi_notification *acpi_notify = vdev->acpi_notification;
712 struct pci_dev *pdev = vdev->pdev;
713 struct acpi_device *adev = ACPI_COMPANION(&pdev->dev);
714 struct notification_queue *entry, *entry_tmp;
715 u64 cnt;
716
717 if (!acpi_notify || !acpi_notify->acpi_notify_trigger)
718 return;
719
720 acpi_remove_notify_handler(adev->handle, ACPI_DEVICE_NOTIFY,
721 vfio_pci_core_acpi_notify);
722
723 eventfd_ctx_remove_wait_queue(acpi_notify->acpi_notify_trigger,
724 &acpi_notify->wait, &cnt);
725
726 flush_work(&acpi_notify->acpi_notification_work);
727
728 mutex_lock(&acpi_notify->notification_list_lock);
729 list_for_each_entry_safe(entry, entry_tmp,
730 &acpi_notify->notification_list,
731 notify_val_next) {
732 list_del(&entry->notify_val_next);
733 kfree(entry);
734 }
735 mutex_unlock(&acpi_notify->notification_list_lock);
736
737 eventfd_ctx_put(acpi_notify->acpi_notify_trigger);
738
739 kfree(acpi_notify);
740
741 vdev->acpi_notification = NULL;
742 }
743 #else
744 void vfio_pci_acpi_notify_close_device(struct vfio_pci_core_device *vdev) {}
745 #endif /* CONFIG_ACPI */
746
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next prev parent reply other threads:[~2023-04-24 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 16:27 [PATCH v2] vfio/pci: Propagate ACPI notifications to user-space via eventfd Grzegorz Jaszczyk
2023-04-24 19:11 ` kernel test robot [this message]
2023-04-24 23:26 ` kernel test robot
2023-04-25 6:31 ` kernel test robot
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=202304250252.8MirvFb0-lkp@intel.com \
--to=lkp@intel.com \
--cc=abhsahu@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=dbehr@chromium.org \
--cc=dbehr@google.com \
--cc=dmy@semihalf.com \
--cc=dtor@google.com \
--cc=jaz@semihalf.com \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=libvir-list@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tn@semihalf.com \
--cc=upstream@semihalf.com \
--cc=yi.l.liu@intel.com \
--cc=yishaih@nvidia.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.