From: kernel test robot <lkp@intel.com>
To: Roger Pau Monne <roger.pau@citrix.com>,
linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
linux-pci@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
"Roger Pau Monne" <roger.pau@citrix.com>,
"Nirmal Patel" <nirmal.patel@linux.intel.com>,
"Jonathan Derrick" <jonathan.derrick@linux.dev>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <helgaas@kernel.org>
Subject: Re: [PATCH 2/3] vmd: disable MSI remapping bypass under Xen
Date: Sun, 12 Jan 2025 10:57:27 +0800 [thread overview]
Message-ID: <202501121029.dJk0TBPr-lkp@intel.com> (raw)
In-Reply-To: <20250110140152.27624-3-roger.pau@citrix.com>
Hi Roger,
kernel test robot noticed the following build errors:
[auto build test ERROR on pci/next]
[also build test ERROR on pci/for-linus tip/irq/core linus/master v6.13-rc6 next-20250110]
[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/Roger-Pau-Monne/xen-pci-do-not-register-devices-outside-of-PCI-segment-scope/20250110-220331
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/20250110140152.27624-3-roger.pau%40citrix.com
patch subject: [PATCH 2/3] vmd: disable MSI remapping bypass under Xen
config: x86_64-buildonly-randconfig-001-20250112 (https://download.01.org/0day-ci/archive/20250112/202501121029.dJk0TBPr-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250112/202501121029.dJk0TBPr-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/202501121029.dJk0TBPr-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/pci/controller/vmd.c: In function 'vmd_probe':
>> drivers/pci/controller/vmd.c:973:13: error: implicit declaration of function 'xen_domain' [-Werror=implicit-function-declaration]
973 | if (xen_domain())
| ^~~~~~~~~~
cc1: some warnings being treated as errors
vim +/xen_domain +973 drivers/pci/controller/vmd.c
966
967 static int vmd_probe(struct pci_dev *dev, const struct pci_device_id *id)
968 {
969 unsigned long features = (unsigned long) id->driver_data;
970 struct vmd_dev *vmd;
971 int err;
972
> 973 if (xen_domain())
974 /*
975 * Xen doesn't have knowledge about devices in the VMD bus.
976 * Bypass of MSI remapping won't work in that case as direct
977 * write to the MSI entries won't result in functional
978 * interrupts.
979 */
980 features &= ~VMD_FEAT_CAN_BYPASS_MSI_REMAP;
981
982 if (resource_size(&dev->resource[VMD_CFGBAR]) < (1 << 20))
983 return -ENOMEM;
984
985 vmd = devm_kzalloc(&dev->dev, sizeof(*vmd), GFP_KERNEL);
986 if (!vmd)
987 return -ENOMEM;
988
989 vmd->dev = dev;
990 vmd->instance = ida_alloc(&vmd_instance_ida, GFP_KERNEL);
991 if (vmd->instance < 0)
992 return vmd->instance;
993
994 vmd->name = devm_kasprintf(&dev->dev, GFP_KERNEL, "vmd%d",
995 vmd->instance);
996 if (!vmd->name) {
997 err = -ENOMEM;
998 goto out_release_instance;
999 }
1000
1001 err = pcim_enable_device(dev);
1002 if (err < 0)
1003 goto out_release_instance;
1004
1005 vmd->cfgbar = pcim_iomap(dev, VMD_CFGBAR, 0);
1006 if (!vmd->cfgbar) {
1007 err = -ENOMEM;
1008 goto out_release_instance;
1009 }
1010
1011 pci_set_master(dev);
1012 if (dma_set_mask_and_coherent(&dev->dev, DMA_BIT_MASK(64)) &&
1013 dma_set_mask_and_coherent(&dev->dev, DMA_BIT_MASK(32))) {
1014 err = -ENODEV;
1015 goto out_release_instance;
1016 }
1017
1018 if (features & VMD_FEAT_OFFSET_FIRST_VECTOR)
1019 vmd->first_vec = 1;
1020
1021 spin_lock_init(&vmd->cfg_lock);
1022 pci_set_drvdata(dev, vmd);
1023 err = vmd_enable_domain(vmd, features);
1024 if (err)
1025 goto out_release_instance;
1026
1027 dev_info(&vmd->dev->dev, "Bound to PCI domain %04x\n",
1028 vmd->sysdata.domain);
1029 return 0;
1030
1031 out_release_instance:
1032 ida_free(&vmd_instance_ida, vmd->instance);
1033 return err;
1034 }
1035
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-01-12 2:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 14:01 [PATCH 0/3] xen: fix usage of devices behind a VMD bridge Roger Pau Monne
2025-01-10 14:01 ` [PATCH 1/3] xen/pci: do not register devices outside of PCI segment scope Roger Pau Monne
2025-01-10 22:21 ` Bjorn Helgaas
2025-01-13 7:20 ` Jan Beulich
2025-01-13 10:18 ` Roger Pau Monné
2025-01-13 23:29 ` Bjorn Helgaas
2025-01-13 7:17 ` Jan Beulich
2025-01-13 10:13 ` Roger Pau Monné
2025-01-10 14:01 ` [PATCH 2/3] vmd: disable MSI remapping bypass under Xen Roger Pau Monne
2025-01-10 22:25 ` Bjorn Helgaas
2025-01-11 5:02 ` Jonathan Derrick
2025-01-13 10:07 ` Roger Pau Monné
2025-01-13 10:03 ` Roger Pau Monné
2025-01-13 15:11 ` Keith Busch
2025-01-13 16:45 ` Roger Pau Monné
2025-01-13 16:53 ` Keith Busch
2025-01-14 11:03 ` Roger Pau Monné
2025-01-12 2:57 ` kernel test robot [this message]
2025-01-10 14:01 ` [PATCH 3/3] pci/msi: remove pci_msi_ignore_mask Roger Pau Monne
2025-01-10 22:30 ` Bjorn Helgaas
2025-01-13 10:25 ` Roger Pau Monné
2025-01-13 23:32 ` Bjorn Helgaas
2025-01-11 11:08 ` kernel test robot
2025-01-11 12:24 ` 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=202501121029.dJk0TBPr-lkp@intel.com \
--to=lkp@intel.com \
--cc=helgaas@kernel.org \
--cc=jonathan.derrick@linux.dev \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=nirmal.patel@linux.intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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