From: Farhan Ali <alifm@linux.ibm.com>
To: linux-s390@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: helgaas@kernel.org, alifm@linux.ibm.com, schnelle@linux.ibm.com,
mjrosato@linux.ibm.com, bblock@linux.ibm.com,
agordeev@linux.ibm.com, gor@linux.ibm.com, hca@linux.ibm.com
Subject: [PATCH v2 0/2] PCI fixes for s390
Date: Wed, 22 Oct 2025 14:24:09 -0700 [thread overview]
Message-ID: <20251022212411.1989-1-alifm@linux.ibm.com> (raw)
Hi,
I came across some issues in PCI code for s390 while working on VFIO error
recovery for s390 PCI devices [1]. These patches can be indepedently applied and
has no depedency on error recovery patch series. We would like to get these
patches merged as they do fix some existing issues.
[1] https://lore.kernel.org/all/20250924171628.826-1-alifm@linux.ibm.com/
ChangeLog
---------
v1 -> v2
- Re-work patch 1 on setting per_func_slot flag. The flag is set if platform
enables per function pci slots (currently only enabled for s390).
- Drop R-b tags for patch 1.
Thanks
Farhan
Farhan Ali (2):
PCI: Allow per function PCI slots
s390/pci: Add architecture specific resource/bus address translation
arch/s390/pci/pci.c | 74 +++++++++++++++++++++++++++++++++++++++
drivers/pci/host-bridge.c | 4 +--
drivers/pci/pci.c | 5 +--
drivers/pci/slot.c | 25 +++++++++++--
include/linux/pci.h | 1 +
5 files changed, 102 insertions(+), 7 deletions(-)
--
2.43.0
next reply other threads:[~2025-10-22 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 21:24 Farhan Ali [this message]
2025-10-22 21:24 ` [PATCH v2 1/2] PCI: Allow per function PCI slots Farhan Ali
2025-10-27 12:29 ` Niklas Schnelle
2025-10-28 1:11 ` Bibo Mao
2025-10-29 8:37 ` Niklas Schnelle
2025-10-22 21:24 ` [PATCH v2 2/2] s390/pci: Add architecture specific resource/bus address translation Farhan Ali
2025-11-03 20:06 ` [PATCH v2 0/2] PCI fixes for s390 Farhan Ali
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=20251022212411.1989-1-alifm@linux.ibm.com \
--to=alifm@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=bblock@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=schnelle@linux.ibm.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).