From: kernel test robot <lkp@intel.com>
To: Matthew W Carlis <mattc@purestorage.com>,
helgaas@kernel.org, bhelgaas@google.com,
sathyanarayanan.kuppuswamy@linux.intel.com,
linux-pci@vger.kernel.org, mika.westerberg@linux.intel.com
Cc: oe-kbuild-all@lists.linux.dev, Matthew W Carlis <mattc@purestorage.com>
Subject: Re: [PATCH 1/1] PCI/portdrv: Allow DPC if the OS controls AER natively.
Date: Tue, 26 Dec 2023 01:53:06 +0800 [thread overview]
Message-ID: <202312260105.Gu2Z5jdw-lkp@intel.com> (raw)
In-Reply-To: <20231223212235.34293-2-mattc@purestorage.com>
Hi Matthew,
kernel test robot noticed the following build errors:
[auto build test ERROR on pci/next]
[also build test ERROR on pci/for-linus linus/master v6.7-rc7 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/Matthew-W-Carlis/PCI-portdrv-Allow-DPC-if-the-OS-controls-AER-natively/20231225-154046
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git next
patch link: https://lore.kernel.org/r/20231223212235.34293-2-mattc%40purestorage.com
patch subject: [PATCH 1/1] PCI/portdrv: Allow DPC if the OS controls AER natively.
config: arc-randconfig-002-20231225 (https://download.01.org/0day-ci/archive/20231226/202312260105.Gu2Z5jdw-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231226/202312260105.Gu2Z5jdw-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/202312260105.Gu2Z5jdw-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/pci/pcie/portdrv.c: In function 'get_port_device_capability':
>> drivers/pci/pcie/portdrv.c:272:19: error: 'struct pci_dev' has no member named 'aer_cap'; did you mean 'ats_cap'?
272 | (dev->aer_cap && host->native_aer)))
| ^~~~~~~
| ats_cap
vim +272 drivers/pci/pcie/portdrv.c
244
245 /* Root Ports and Root Complex Event Collectors may generate PMEs */
246 if ((pci_pcie_type(dev) == PCI_EXP_TYPE_ROOT_PORT ||
247 pci_pcie_type(dev) == PCI_EXP_TYPE_RC_EC) &&
248 (pcie_ports_native || host->native_pme)) {
249 services |= PCIE_PORT_SERVICE_PME;
250
251 /*
252 * Disable PME interrupt on this port in case it's been enabled
253 * by the BIOS (the PME service driver will enable it when
254 * necessary).
255 */
256 pcie_pme_interrupt_enable(dev, false);
257 }
258
259 /*
260 * _OSC AER Control is required by the OS & requires OS to control AER,
261 * but _OSC DPC Control isn't required by the OS to control DPC; however
262 * it does require the OS to control DPC. _OSC DPC Control also requres
263 * _OSC EDR Control (Error Disconnect Recovery) (PCI Firmware - DPC ECN rev3.2)
264 * PCI_Express_Base 6.1, 6.2.11 Determination of DPC Control recommends
265 * platform fw or OS always link control of DPC to AER.
266 *
267 * With dpc-native, allow Linux to use DPC even if it doesn't have
268 * permission to use AER.
269 */
270 if (pci_find_ext_capability(dev, PCI_EXT_CAP_ID_DPC) &&
271 pci_aer_available() && (pcie_ports_dpc_native ||
> 272 (dev->aer_cap && host->native_aer)))
273 services |= PCIE_PORT_SERVICE_DPC;
274
275 if (pci_pcie_type(dev) == PCI_EXP_TYPE_DOWNSTREAM ||
276 pci_pcie_type(dev) == PCI_EXP_TYPE_ROOT_PORT) {
277 u32 linkcap;
278
279 pcie_capability_read_dword(dev, PCI_EXP_LNKCAP, &linkcap);
280 if (linkcap & PCI_EXP_LNKCAP_LBNC)
281 services |= PCIE_PORT_SERVICE_BWNOTIF;
282 }
283
284 return services;
285 }
286
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-12-25 17:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 21:22 [PATCH 1/1] PCI/portdrv: Allow DPC if the OS controls AER natively Matthew W Carlis
2023-12-23 21:22 ` Matthew W Carlis
2023-12-25 17:53 ` kernel test robot [this message]
2023-12-25 20:36 ` kernel test robot
2023-12-26 0:02 ` Matthew W Carlis
2023-12-28 21:23 ` Bjorn Helgaas
2024-01-02 15:41 ` Kuppuswamy Sathyanarayanan
2024-01-08 19:46 ` Matthew W Carlis
2024-01-08 19:53 ` Kuppuswamy Sathyanarayanan
2024-01-09 0:15 ` Matthew W Carlis
2024-01-10 16:41 ` Kuppuswamy Sathyanarayanan
2024-01-10 17:13 ` Kuppuswamy Sathyanarayanan
2024-01-10 20:01 ` Matthew W Carlis
2024-01-10 19:59 ` Matthew W Carlis
2024-01-22 19:32 ` Bjorn Helgaas
2024-01-23 2:37 ` Kuppuswamy Sathyanarayanan
2024-01-23 15:59 ` Bjorn Helgaas
2024-01-23 23:18 ` Matthew W Carlis
2024-01-24 20:29 ` Bjorn Helgaas
2024-02-21 23:11 ` Bjorn Helgaas
2024-02-21 23:33 ` Bjorn Helgaas
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=202312260105.Gu2Z5jdw-lkp@intel.com \
--to=lkp@intel.com \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mattc@purestorage.com \
--cc=mika.westerberg@linux.intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox