From: "Durawa, Szymon" <szymon.durawa@linux.intel.com>
To: helgaas@kernel.org
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Dan Williams <dan.j.williams@intel.com>,
Lukas Wunner <lukas@wunner.de>,
linux-pci@vger.kernel.org,
Nirmal Patel <nirmal.patel@linux.intel.com>,
Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
Subject: Re: [PATCH v3 0/8] VMD add second rootbus support
Date: Mon, 27 Jan 2025 21:59:35 +0100 [thread overview]
Message-ID: <91b733bf-b133-47f1-9dff-440d75bd6fd4@linux.intel.com> (raw)
In-Reply-To: <20241122085215.424736-1-szymon.durawa@linux.intel.com>
On 11/22/2024 9:52 AM, Szymon Durawa wrote:
> This patch series implements second rootbus support inside Intel VMD module.
> Current implementation allows VMD to take ownership of devices only on first
> bus (Rootbus0). Starting from Intel Arrow Lake, VMD exposes second bus
> (Rootbus1) to allow VMD to own devices on this bus as well. VMD MMIO BARs
> (CFGBAR. MEMBAR1 and MEMBAR2) are now shared between Rootbus0 and Rootbus1.
> Reconfiguration of 3 MMIO BARs is required by resizing current MMIO BARs ranges.
> It allows to find/register VMD Rootbus1 and discovers devices or root
> ports under it.
>
> Patches 1 to 6 introduce code refactoring without functional changes.
> Patch 7 implements VMD Rootbus1 support and patch 8 provides workaround for
> rootbus number hardwired to fixed non-zero value. Patch 8 is necessary for
> correct enumeration attached devices under VMD Rootbus1. Without it user cannot
> access those devices as they are not visible in the system, only drives under
> VMD Rootbus0 are available to the user.
>
> Changes from v1:
> - splitting series into more commits, requested by Bjorn
> - adding helper functions, suggested by Bjorn
> - minor typos and unclear wording updated, suggested by Bjorn
>
> Changes from v2:
> - wording update in commit logs, suggested by Bjorn
>
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Lukas Wunner <lukas@wunner.de>
> Cc: linux-pci@vger.kernel.org
> Suggested-by: Nirmal Patel <nirmal.patel@linux.intel.com>
> Reviewed-by: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
> Signed-off-by: Szymon Durawa <szymon.durawa@linux.intel.com>
>
> Szymon Durawa (8):
> PCI: vmd: Add vmd_bus_enumeration()
> PCI: vmd: Add vmd_configure_cfgbar()
> PCI: vmd: Add vmd_configure_membar() and
> vmd_configure_membar1_membar2()
> PCI: vmd: Add vmd_create_bus()
> PCI: vmd: Replace hardcoded values with enum and defines
> PCI: vmd: Convert bus and busn_start to an array
> PCI: vmd: Add support for second rootbus under VMD
> PCI: vmd: Add workaround for bus number hardwired to fixed non-zero
> value
>
> drivers/pci/controller/vmd.c | 470 +++++++++++++++++++++++++++--------
> 1 file changed, 360 insertions(+), 110 deletions(-)
> mode change 100644 => 100755 drivers/pci/controller/vmd.c
Hello Bjorn,
Gentle ping. I addressed all of your previous comments, please take a
look at v3 patch.
Thanks,
Szymon
prev parent reply other threads:[~2025-01-27 20:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 8:52 [PATCH v3 0/8] VMD add second rootbus support Szymon Durawa
2024-11-22 8:52 ` [PATCH v3 1/8] PCI: vmd: Add vmd_bus_enumeration() Szymon Durawa
2024-11-22 8:52 ` [PATCH v3 2/8] PCI: vmd: Add vmd_configure_cfgbar() Szymon Durawa
2024-11-22 8:52 ` [PATCH v3 3/8] PCI: vmd: Add vmd_configure_membar() and vmd_configure_membar1_membar2() Szymon Durawa
2024-11-22 8:52 ` [PATCH v3 4/8] PCI: vmd: Add vmd_create_bus() Szymon Durawa
2024-11-22 8:52 ` [PATCH v3 5/8] PCI: vmd: Replace hardcoded values with enum and defines Szymon Durawa
2025-05-05 17:33 ` Bjorn Helgaas
2024-11-22 8:52 ` [PATCH v3 6/8] PCI: vmd: Convert bus and busn_start to an array Szymon Durawa
2024-11-22 8:52 ` [PATCH v3 7/8] PCI: vmd: Add support for second rootbus under VMD Szymon Durawa
2025-05-03 13:20 ` Manivannan Sadhasivam
2025-05-05 17:31 ` Bjorn Helgaas
2024-11-22 8:52 ` [PATCH v3 8/8] PCI: vmd: Add workaround for bus number hardwired to fixed non-zero value Szymon Durawa
2025-05-05 17:31 ` Bjorn Helgaas
2025-01-27 20:59 ` Durawa, Szymon [this message]
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=91b733bf-b133-47f1-9dff-440d75bd6fd4@linux.intel.com \
--to=szymon.durawa@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=nirmal.patel@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