From: Stefano Stabellini <sstabellini@kernel.org>
To: Bernhard Beschow <shentey@gmail.com>, mst@redhat.com
Cc: qemu-devel@nongnu.org,
"Richard Henderson" <richard.henderson@linaro.org>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"David Woodhouse" <dwmw@amazon.co.uk>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Chuck Zmudzinski" <brchuckz@aol.com>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Paul Durrant" <paul@xen.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Anthony Perard" <anthony.perard@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v4 0/7] Resolve TYPE_PIIX3_XEN_DEVICE
Date: Mon, 15 May 2023 13:52:40 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2305151350180.4125828@ubuntu-linux-20-04-desktop> (raw)
In-Reply-To: <9EB9A984-61E5-4226-8352-B5DDC6E2C62E@gmail.com>
On Sat, 13 May 2023, Bernhard Beschow wrote:
> Am 21. April 2023 07:38:10 UTC schrieb "Michael S. Tsirkin" <mst@redhat.com>:
> >On Mon, Apr 03, 2023 at 09:41:17AM +0200, Bernhard Beschow wrote:
> >> There is currently a dedicated PIIX3 device model for use under Xen. By reusing
> >> existing PCI API during initialization this device model can be eliminated and
> >> the plain PIIX3 device model can be used instead.
> >>
> >> Resolving TYPE_PIIX3_XEN_DEVICE results in less code while also making Xen
> >> agnostic towards the precise south bridge being used in the PC machine. The
> >> latter might become particularily interesting once PIIX4 becomes usable in the
> >> PC machine, avoiding the "Frankenstein" use of PIIX4_ACPI in PIIX3.
> >
> >xen stuff so I assume that tree?
>
> Ping
I am OK either way. Michael, what do you prefer?
Normally I would suggest for you to pick up the patches. But as it
happens I'll have to likely send another pull request in a week or two
and I can add these patches to it.
Let me know your preference and I am happy to follow it.
> >
> >> Testing done:
> >> - `make check`
> >> - Run `xl create` with the following config:
> >> name = "Manjaro"
> >> type = 'hvm'
> >> memory = 1536
> >> apic = 1
> >> usb = 1
> >> disk = [ "file:manjaro-kde-21.2.6-220416-linux515.iso,hdc:cdrom,r" ]
> >> device_model_override = "/usr/bin/qemu-system-x86_64"
> >> vga = "stdvga"
> >> sdl = 1
> >> - `qemu-system-x86_64 -M pc -m 2G -cpu host -accel kvm \
> >> -cdrom manjaro-kde-21.2.6-220416-linux515.iso`
> >>
> >> v4:
> >> - Add patch fixing latent memory leak in pci_bus_irqs() (Anthony)
> >>
> >> v3:
> >> - Rebase onto master
> >>
> >> v2:
> >> - xen_piix3_set_irq() is already generic. Just rename it. (Chuck)
> >>
> >> Tested-by: Chuck Zmudzinski <brchuckz@aol.com>
> >>
> >> Bernhard Beschow (7):
> >> include/hw/xen/xen: Rename xen_piix3_set_irq() to xen_intx_set_irq()
> >> hw/pci/pci.c: Don't leak PCIBus::irq_count[] in pci_bus_irqs()
> >> hw/isa/piix3: Reuse piix3_realize() in piix3_xen_realize()
> >> hw/isa/piix3: Wire up Xen PCI IRQ handling outside of PIIX3
> >> hw/isa/piix3: Avoid Xen-specific variant of piix3_write_config()
> >> hw/isa/piix3: Resolve redundant k->config_write assignments
> >> hw/isa/piix3: Resolve redundant TYPE_PIIX3_XEN_DEVICE
> >>
> >> include/hw/southbridge/piix.h | 1 -
> >> include/hw/xen/xen.h | 2 +-
> >> hw/i386/pc_piix.c | 36 +++++++++++++++++++--
> >> hw/i386/xen/xen-hvm.c | 2 +-
> >> hw/isa/piix3.c | 60 +----------------------------------
> >> hw/pci/pci.c | 2 ++
> >> stubs/xen-hw-stub.c | 2 +-
> >> 7 files changed, 39 insertions(+), 66 deletions(-)
> >>
> >> --
> >> 2.40.0
> >>
> >
>
next prev parent reply other threads:[~2023-05-15 20:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 7:41 [PATCH v4 0/7] Resolve TYPE_PIIX3_XEN_DEVICE Bernhard Beschow
2023-04-03 7:41 ` [PATCH v4 1/7] include/hw/xen/xen: Rename xen_piix3_set_irq() to xen_intx_set_irq() Bernhard Beschow
2023-04-03 7:41 ` [PATCH v4 2/7] hw/pci/pci.c: Don't leak PCIBus::irq_count[] in pci_bus_irqs() Bernhard Beschow
2023-04-19 19:31 ` Bernhard Beschow
2023-04-21 7:37 ` Michael S. Tsirkin
2023-04-03 7:41 ` [PATCH v4 3/7] hw/isa/piix3: Reuse piix3_realize() in piix3_xen_realize() Bernhard Beschow
2023-04-03 7:41 ` [PATCH v4 4/7] hw/isa/piix3: Wire up Xen PCI IRQ handling outside of PIIX3 Bernhard Beschow
2023-04-03 7:41 ` [PATCH v4 5/7] hw/isa/piix3: Avoid Xen-specific variant of piix3_write_config() Bernhard Beschow
2023-04-03 7:41 ` [PATCH v4 6/7] hw/isa/piix3: Resolve redundant k->config_write assignments Bernhard Beschow
2023-04-03 7:41 ` [PATCH v4 7/7] hw/isa/piix3: Resolve redundant TYPE_PIIX3_XEN_DEVICE Bernhard Beschow
2023-04-21 7:38 ` [PATCH v4 0/7] Resolve TYPE_PIIX3_XEN_DEVICE Michael S. Tsirkin
2023-04-21 16:35 ` Bernhard Beschow
2023-05-13 11:44 ` Bernhard Beschow
2023-05-15 20:52 ` Stefano Stabellini [this message]
2023-05-22 15:42 ` Bernhard Beschow
2023-06-05 7:01 ` Bernhard Beschow
2023-06-08 22:43 ` Stefano Stabellini
2023-06-09 0:23 ` Stefano Stabellini
2023-06-09 10:46 ` Anthony PERARD
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=alpine.DEB.2.22.394.2305151350180.4125828@ubuntu-linux-20-04-desktop \
--to=sstabellini@kernel.org \
--cc=anthony.perard@citrix.com \
--cc=aurelien@aurel32.net \
--cc=brchuckz@aol.com \
--cc=dwmw@amazon.co.uk \
--cc=eduardo@habkost.net \
--cc=hpoussin@reactos.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shentey@gmail.com \
--cc=xen-devel@lists.xenproject.org \
/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).