From: "Michael S. Tsirkin" <mst@redhat.com>
To: Bernhard Beschow <shentey@gmail.com>
Cc: qemu-devel@nongnu.org,
"John G Johnson" <john.g.johnson@oracle.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Huacai Chen" <chenhuacai@kernel.org>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Elena Ufimtseva" <elena.ufimtseva@oracle.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Jagannathan Raman" <jag.raman@oracle.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-ppc@nongnu.org, qemu-arm@nongnu.org
Subject: Re: [PATCH v2 0/3] Decouple INTx-to-LNKx routing from south bridges
Date: Wed, 21 Dec 2022 01:32:58 -0500 [thread overview]
Message-ID: <20221221013252-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221120150550.63059-1-shentey@gmail.com>
On Sun, Nov 20, 2022 at 04:05:47PM +0100, Bernhard Beschow wrote:
> v1:
> ===
>
> During my PIIX consolidation work [1] I've noticed that both PIIX models have
> quite different pci_slot_get_pirq() implementations. These functions seem to
> map PCI INTx pins to input pins of a programmable interrupt router which is
> AFAIU board-specific. IOW, board-specific assumptions are baked into the device
> models which prevent e.g. the whole PIIX4 south bridge to be reusable in the PC
> machine.
>
> This series first factors out pci_bus_map_irqs() from pci_bus_irqs() which
> then allowes for moving the two board-specific PIIX pci_slot_get_pirq()
> funtions into their respective boards. With these changes, the PIIX4 south
> bridge could eventually become an alternative to the PIIX3-Frankenstein
> solution in the PC machine.
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> v2:
> ===
> * Remove RFC tag from whole series
> * New patch to split pci_bus_irqs()
> * Remove VT82xx patch which was just a demonstration
>
> Testing done:
> * `make check`
> * `make check-avocado`
> * `qemu-system-mips64el -M malta -kernel vmlinux-3.2.0-4-5kc-malta -hda debian_wheezy_mipsel_standard.qcow2 -append "root=/dev/sda1 console=ttyS0"`
> * `qemu-system-x86_64 -M pc -m 2G -cdrom manjaro-kde-21.3.2-220704-linux515.iso`
>
> Thanks,
> Bernhard
>
> [1] https://lists.nongnu.org/archive/html/qemu-devel/2022-10/msg03941.html
>
> Bernhard Beschow (3):
> hw/pci/pci: Factor out pci_bus_map_irqs() from pci_bus_irqs()
> hw/isa/piix3: Decouple INTx-to-LNKx routing which is board-specific
> hw/isa/piix4: Decouple INTx-to-LNKx routing which is board-specific
>
> hw/i386/pc_piix.c | 16 ++++++++++++++++
> hw/i386/pc_q35.c | 4 ++--
> hw/isa/piix3.c | 17 ++---------------
> hw/isa/piix4.c | 27 +--------------------------
> hw/mips/malta.c | 28 ++++++++++++++++++++++++++++
> hw/pci-host/raven.c | 3 ++-
> hw/pci-host/versatile.c | 3 ++-
> hw/pci/pci.c | 12 +++++++++---
> hw/remote/machine.c | 3 ++-
> include/hw/pci/pci.h | 3 ++-
> 10 files changed, 66 insertions(+), 50 deletions(-)
>
> --
> 2.38.1
>
next prev parent reply other threads:[~2022-12-21 6:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-20 15:05 [PATCH v2 0/3] Decouple INTx-to-LNKx routing from south bridges Bernhard Beschow
2022-11-20 15:05 ` [PATCH v2 1/3] hw/pci/pci: Factor out pci_bus_map_irqs() from pci_bus_irqs() Bernhard Beschow
2022-11-20 15:05 ` [PATCH v2 2/3] hw/isa/piix3: Decouple INTx-to-LNKx routing which is board-specific Bernhard Beschow
2022-11-20 15:05 ` [PATCH v2 3/3] hw/isa/piix4: " Bernhard Beschow
2022-12-09 15:23 ` [PATCH v2 0/3] Decouple INTx-to-LNKx routing from south bridges Philippe Mathieu-Daudé
2022-12-18 10:21 ` Bernhard Beschow
2022-12-18 13:05 ` Michael S. Tsirkin
2022-12-20 23:10 ` Michael S. Tsirkin
2022-12-20 23:26 ` Bernhard Beschow
2022-12-21 6:33 ` Michael S. Tsirkin
2022-12-21 6:32 ` Michael S. Tsirkin [this message]
2022-12-21 7:24 ` Philippe Mathieu-Daudé
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=20221221013252-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=aurelien@aurel32.net \
--cc=chenhuacai@kernel.org \
--cc=eduardo@habkost.net \
--cc=elena.ufimtseva@oracle.com \
--cc=hpoussin@reactos.org \
--cc=jag.raman@oracle.com \
--cc=jiaxun.yang@flygoat.com \
--cc=john.g.johnson@oracle.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shentey@gmail.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).