From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Sergio Lopez <slp@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH 0/4] RfC: microvm: add second ioapic
Date: Fri, 16 Oct 2020 15:16:20 +0200 [thread overview]
Message-ID: <ffd81f03-b2a0-2c58-9f13-c956dfd1ca17@redhat.com> (raw)
In-Reply-To: <20201016114328.18835-1-kraxel@redhat.com>
On 10/16/20 1:43 PM, Gerd Hoffmann wrote:
> Add a second ioapic to microvm. Gives us more IRQ lines we can
> use for virtio-mmio devices. Bump number of possible virtio-mmio
> devices from 8 to 24.
>
> Gerd Hoffmann (4):
> microvm: make number of virtio transports runtime configurable
> microvm: make pcie irq base runtime configurable
> microvm: add second ioapic
> microvm: reconfigure irqs if second ioapic is available
After looking at Laurent's m68k virt machine,
I wonder if it is possible to use the Goldfish-PIC
with the MicroVM instead (or another Goldfish machine
type).
next prev parent reply other threads:[~2020-10-16 13:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 11:43 [PATCH 0/4] RfC: microvm: add second ioapic Gerd Hoffmann
2020-10-16 11:43 ` [PATCH 1/4] microvm: make number of virtio transports runtime configurable Gerd Hoffmann
2020-10-23 19:00 ` Igor Mammedov
2020-10-26 7:04 ` Gerd Hoffmann
2020-10-16 11:43 ` [PATCH 2/4] microvm: make pcie irq base " Gerd Hoffmann
2020-10-23 18:58 ` Igor Mammedov
2020-10-16 11:43 ` [PATCH 3/4] microvm: add second ioapic Gerd Hoffmann
2020-10-23 18:56 ` Igor Mammedov
2020-10-16 11:43 ` [PATCH 4/4] microvm: reconfigure irqs if second ioapic is available Gerd Hoffmann
2020-10-23 18:52 ` Igor Mammedov
2020-10-26 8:25 ` Gerd Hoffmann
2020-10-16 13:16 ` Philippe Mathieu-Daudé [this message]
2020-10-19 7:07 ` [PATCH 0/4] RfC: microvm: add second ioapic Gerd Hoffmann
2020-10-19 8:32 ` Philippe Mathieu-Daudé
2020-10-19 9:09 ` Gerd Hoffmann
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=ffd81f03-b2a0-2c58-9f13-c956dfd1ca17@redhat.com \
--to=philmd@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kraxel@redhat.com \
--cc=lvivier@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=slp@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.