From: kernel test robot <lkp@intel.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>,
linux-pci@vger.kernel.org, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Bjorn Helgaas" <helgaas@kernel.org>,
"Christian König" <christian.koenig@amd.com>,
"Krzysztof Wilczyński" <kw@linux.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Michal Wajdeczko" <michal.wajdeczko@intel.com>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Matt Roper" <matthew.d.roper@intel.com>,
"Michał Winiarski" <michal.winiarski@intel.com>
Subject: Re: [PATCH v2 1/3] PCI: Add support for VF Resizable Bar extended cap
Date: Fri, 20 Sep 2024 16:36:58 +0800 [thread overview]
Message-ID: <202409201629.QlC0MRbn-lkp@intel.com> (raw)
In-Reply-To: <20240919223557.1897608-2-michal.winiarski@intel.com>
Hi Michał,
kernel test robot noticed the following build warnings:
[auto build test WARNING on pci/for-linus]
[also build test WARNING on drm-xe/drm-xe-next drm/drm-next drm-exynos/exynos-drm-next drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-misc/drm-misc-next drm-tip/drm-tip linus/master v6.11 next-20240919]
[cannot apply to pci/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/Micha-Winiarski/PCI-Add-support-for-VF-Resizable-Bar-extended-cap/20240920-064112
base: https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git for-linus
patch link: https://lore.kernel.org/r/20240919223557.1897608-2-michal.winiarski%40intel.com
patch subject: [PATCH v2 1/3] PCI: Add support for VF Resizable Bar extended cap
config: x86_64-kexec (https://download.01.org/0day-ci/archive/20240920/202409201629.QlC0MRbn-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240920/202409201629.QlC0MRbn-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/202409201629.QlC0MRbn-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/pci/pci.c:1920:20: warning: variable 'res' set but not used [-Wunused-but-set-variable]
1920 | struct resource *res;
| ^
1 warning generated.
vim +/res +1920 drivers/pci/pci.c
1903
1904 static void pci_restore_vf_rebar_state(struct pci_dev *pdev)
1905 {
1906 unsigned int pos, nbars, i;
1907 u32 ctrl;
1908
1909 if (!pdev->is_physfn)
1910 return;
1911
1912 pos = pci_find_ext_capability(pdev, PCI_EXT_CAP_ID_VF_REBAR);
1913 if (!pos)
1914 return;
1915
1916 pci_read_config_dword(pdev, pos + PCI_REBAR_CTRL, &ctrl);
1917 nbars = FIELD_GET(PCI_REBAR_CTRL_NBAR_MASK, ctrl);
1918
1919 for (i = 0; i < nbars; i++, pos += 8) {
> 1920 struct resource *res;
1921 int bar_idx, size;
1922
1923 pci_read_config_dword(pdev, pos + PCI_REBAR_CTRL, &ctrl);
1924 bar_idx = ctrl & PCI_REBAR_CTRL_BAR_IDX;
1925 res = pdev->resource + bar_idx;
1926 size = pci_rebar_bytes_to_size(pdev->sriov->barsz[bar_idx]);
1927 ctrl &= ~PCI_REBAR_CTRL_BAR_SIZE;
1928 ctrl |= FIELD_PREP(PCI_REBAR_CTRL_BAR_SIZE, size);
1929 pci_write_config_dword(pdev, pos + PCI_REBAR_CTRL, ctrl);
1930 }
1931 }
1932
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-20 8:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 22:35 [PATCH v2 0/3] PCI: VF resizable BAR Michał Winiarski
2024-09-19 22:35 ` [PATCH v2 1/3] PCI: Add support for VF Resizable Bar extended cap Michał Winiarski
2024-09-20 8:36 ` kernel test robot [this message]
2024-09-20 9:57 ` Christian König
2024-10-10 8:46 ` Michał Winiarski
2024-09-19 22:35 ` [PATCH v2 2/3] PCI: Allow extending VF BAR within original resource boundary Michał Winiarski
2024-09-20 10:07 ` Christian König
2024-10-10 8:59 ` Michał Winiarski
[not found] ` <8fa25483-d6e2-4614-aa2a-c41af0529e5c@amd.com>
2024-10-11 9:23 ` Christian König
2024-09-20 11:09 ` kernel test robot
2024-09-20 11:19 ` kernel test robot
2024-09-20 11:30 ` Ilpo Järvinen
2024-10-10 8:43 ` Michał Winiarski
2024-09-19 22:35 ` [PATCH v2 3/3] drm/xe/pf: Extend the VF LMEM BAR Michał Winiarski
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=202409201629.QlC0MRbn-lkp@intel.com \
--to=lkp@intel.com \
--cc=airlied@gmail.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=helgaas@kernel.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.d.roper@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=michal.winiarski@intel.com \
--cc=mripard@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).