From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Marcin Bernatowicz" <marcin.bernatowicz@linux.intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.checkpatch: warning for PCI/IOV: Restore initial VF BAR sizing after VF ReBAR
Date: Tue, 05 May 2026 17:05:59 -0000 [thread overview]
Message-ID: <177800075934.38316.4169518354059583757@5ab824fced77> (raw)
In-Reply-To: <20260505170010.3414074-1-marcin.bernatowicz@linux.intel.com>
== Series Details ==
Series: PCI/IOV: Restore initial VF BAR sizing after VF ReBAR
URL : https://patchwork.freedesktop.org/series/166011/
State : warning
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
c8c12e558adaef7a4d125d83b6e1f8824bc13b82
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 483916a4015a42fcfc4d9d894aa53a52c2abb16d
Author: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
Date: Tue May 5 19:00:10 2026 +0200
PCI/IOV: Restore initial VF ReBAR sizes on PF release
sriov_disable() and sriov_enable() error paths restore the per-VF BAR
sizes saved at probe time. They do not cover the case where the PF
driver is unbound while VF BARs were resized but SR-IOV was never
enabled (or was already disabled).
On the next bind, sriov_init() re-reads the SR-IOV capability and
captures the current (inflated) BAR registers as the new initial sizes
in iov->barsz_orig[]. The restore logic becomes a no-op for that boot
and the kernel may reserve MMIO for the inflated VF aperture multiplied
by TotalVFs.
Restore the initial sizes from sriov_release() as well. At this point
num_VFs is 0 (BUG_ON enforces it) and VF Memory Space is therefore
disabled, satisfying the precondition of pci_iov_vf_bar_set_size().
Signed-off-by: Marcin Bernatowicz <marcin.bernatowicz@linux.intel.com>
+ /mt/dim checkpatch 0642e494a060664ccd22c0dcdd7b34043518f0a7 drm-intel
7f507bed2ac9 PCI/IOV: Remember initial VF BAR sizes
e283ad731ca1 PCI/IOV: Restore initial VF ReBAR sizes on SR-IOV disable/failure
-:109: WARNING:ENOSYS: ENOSYS means 'invalid syscall nr' and nothing else
#109: FILE: drivers/pci/iov.c:751:
+ rc = -ENOSYS;
total: 0 errors, 1 warnings, 0 checks, 108 lines checked
483916a4015a PCI/IOV: Restore initial VF ReBAR sizes on PF release
next prev parent reply other threads:[~2026-05-05 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 17:00 [PATCH 0/3] PCI/IOV: Restore initial VF BAR sizing after VF ReBAR Marcin Bernatowicz
2026-05-05 17:00 ` [PATCH 1/3] PCI/IOV: Remember initial VF BAR sizes Marcin Bernatowicz
2026-05-05 17:00 ` [PATCH 2/3] PCI/IOV: Restore initial VF ReBAR sizes on SR-IOV disable/failure Marcin Bernatowicz
2026-05-05 17:00 ` [PATCH 3/3] PCI/IOV: Restore initial VF ReBAR sizes on PF release Marcin Bernatowicz
2026-05-05 17:05 ` Patchwork [this message]
2026-05-05 17:07 ` ✓ CI.KUnit: success for PCI/IOV: Restore initial VF BAR sizing after VF ReBAR Patchwork
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=177800075934.38316.4169518354059583757@5ab824fced77 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=marcin.bernatowicz@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).