From: Nabih Estefan <nabihestefan@google.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, mst@redhat.com, marcel.apfelbaum@gmail.com,
venture@google.com
Subject: Re: [PATCH 0/2] hw/pci-bridge: Create PLX Virtual Switch Device
Date: Mon, 15 Sep 2025 11:59:02 -0700 [thread overview]
Message-ID: <CA+QoejUmDgKMuTbWY_1-7ok1spag-ANP-+TvsMgytkka+5PBdg@mail.gmail.com> (raw)
In-Reply-To: <20250826205532.1500639-1-nabihestefan@google.com>
Friendly ping on the review!
Thanks,
Nabih
On Tue, Aug 26, 2025 at 1:55 PM Nabih Estefan <nabihestefan@google.com> wrote:
>
> Create a PLX PEX PCIe Virtual Switch implementation that can be used
> for modeling trays. This is a generalized version of the xio3130 switch where
> we can set the PCI information on creation, allowing us to model different
> trays without creating specific devices for all of them. It is used the same
> way the xio3130 switch is used + the PCI Signature information.
>
> The idea is to minimize the difficulty of creating different trays whose
> only difference is recognition by some daemon through PCI signatures.
> Instead of having to create 8 different versions of xio3130 that have
> the same functionality but different PCI Signatures, we create one
> general version where you can declare the PCI Signature information,
> while keeping the same base functionality. This is not meant to fully
> replace xio3130 since that is easier to use without knowledge of the PCI
> Signature, this is meant to decrease the difficulty of creating switch
> trays that require certain PCI information for recognition without any
> significant change from a normal PLX Virtual Switch functionality.
>
> Changes from v1&2: Updating different formatting and API changes that
> ocurred QEMU-wide since these patches were first staged in 8.1.
>
> Signed-off-by: Nabih Estefan <nabihestefan@google.com>
> Signed-off-by: Patrick Venture <venture@google.com>
>
> Nabih Estefan (2):
> hw/pci-bridge: Create Initial revision for PLX Virtual Switch
> MAINTAINERS: Add entry for PLX VSwitches
>
> MAINTAINERS | 6 +
> hw/pci-bridge/Kconfig | 5 +
> hw/pci-bridge/meson.build | 1 +
> hw/pci-bridge/plx_vswitch_downstream.c | 188 +++++++++++++++++++++++++
> hw/pci-bridge/plx_vswitch_upstream.c | 178 +++++++++++++++++++++++
> include/hw/pci-bridge/plx_vswitch.h | 43 ++++++
> 6 files changed, 421 insertions(+)
> create mode 100644 hw/pci-bridge/plx_vswitch_downstream.c
> create mode 100644 hw/pci-bridge/plx_vswitch_upstream.c
> create mode 100644 include/hw/pci-bridge/plx_vswitch.h
>
> --
> 2.51.0.318.gd7df087d1a-goog
>
next prev parent reply other threads:[~2025-09-15 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 20:55 [PATCH 0/2] hw/pci-bridge: Create PLX Virtual Switch Device Nabih Estefan
2025-08-26 20:55 ` [PATCH 1/2] hw/pci-bridge: Create Initial revision for PLX Virtual Switch Nabih Estefan
2025-08-26 20:55 ` [PATCH 2/2] MAINTAINERS: Add entry for PLX VSwitches Nabih Estefan
2025-09-15 18:59 ` Nabih Estefan [this message]
2025-09-16 8:38 ` [PATCH 0/2] hw/pci-bridge: Create PLX Virtual Switch Device Peter Maydell
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=CA+QoejUmDgKMuTbWY_1-7ok1spag-ANP-+TvsMgytkka+5PBdg@mail.gmail.com \
--to=nabihestefan@google.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=venture@google.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 NNTP newsgroup(s).