From: Marc Zyngier <marc.zyngier@arm.com>
To: Eric Auger <eric.auger@redhat.com>
Cc: zhang.zhanghailiang@huawei.com, kvm@vger.kernel.org,
andre.przywara@arm.com, linux-kernel@vger.kernel.org,
qemu-arm@nongnu.org, kvmarm@lists.cs.columbia.edu,
eric.auger.pro@gmail.com
Subject: Re: [PATCH] KVM: arm/arm64: vgic: Use a single IO device per redistributor
Date: Sun, 25 Aug 2019 11:04:35 +0100 [thread overview]
Message-ID: <86y2zhmuh8.wl-marc.zyngier@arm.com> (raw)
In-Reply-To: <20190823173330.23342-1-eric.auger@redhat.com>
On Fri, 23 Aug 2019 18:33:30 +0100,
Eric Auger <eric.auger@redhat.com> wrote:
>
> At the moment we use 2 IO devices per GICv3 redistributor: one
> one for the RD_base frame and one for the SGI_base frame.
>
> Instead we can use a single IO device per redistributor (the 2
> frames are contiguous). This saves slots on the KVM_MMIO_BUS
> which is currently limited to NR_IOBUS_DEVS (1000).
>
> This change allows to instantiate up to 512 redistributors and may
> speed the guest boot with a large number of VCPUs.
>
> Signed-off-by: Eric Auger <eric.auger@redhat.com>
Yup, that's exactly what I was hoping for. A very nice cleanup, and no
need to increase NR_IOBUS_DEVS for the foreseeable future.
I've applied this to -next.
Thanks,
M.
--
Jazz is not dead, it just smells funny.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
prev parent reply other threads:[~2019-08-25 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 17:33 [PATCH] KVM: arm/arm64: vgic: Use a single IO device per redistributor Eric Auger
2019-08-23 17:52 ` Auger Eric
2019-08-25 10:20 ` Marc Zyngier
2019-08-27 7:49 ` Zenghui Yu
2019-08-27 7:53 ` Auger Eric
2019-08-25 10:04 ` Marc Zyngier [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=86y2zhmuh8.wl-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--cc=andre.przywara@arm.com \
--cc=eric.auger.pro@gmail.com \
--cc=eric.auger@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=qemu-arm@nongnu.org \
--cc=zhang.zhanghailiang@huawei.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).