From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 0/5] arm/arm64: KVM: dynamic VGIC sizing
Date: Mon, 21 Oct 2013 15:02:51 +0100 [thread overview]
Message-ID: <20131021140251.GD39411@lvm> (raw)
In-Reply-To: <1380888978-27725-1-git-send-email-marc.zyngier@arm.com>
On Fri, Oct 04, 2013 at 01:16:13PM +0100, Marc Zyngier wrote:
> So far, the VGIC data structures have been statically sized, meaning
> that we always have to support more interrupts than we actually want,
> and more CPU interfaces than we should.
>
> This is a waste of resource, and is the kind of things that should be
> tuneable. This series partially addresses that issue by changing the
> data structures to be dynamically allocated.
>
> The various sizes are still static, but the VGIC code itself doesn't
> have any reference to these anymore. Once plugged into the new device
> API, we should be able to size it entierely dynamically.
>
> I'm hopping for this series to be merged with Christoffer's VGIC
> device control API.
Review it and you can stop hopping (must be hard on your legs).
I'll be happy to help with the merge ;)
>
> This has been (lightly) tested on both ARM (TC2) and arm64 (model).
>
> M.
>
> Marc Zyngier (5):
> arm/arm64: KVM: vgic: switch to dynamic allocation
> arm/arm64: KVM: vgic: kill VGIC_NR_SHARED_IRQS
> arm/arm64: KVM: vgic: kill VGIC_MAX_CPUS
> arm/arm64: KVM: vgic: handle out-of-range MMIO accesses
> arm/arm64: KVM: vgic: kill VGIC_NR_IRQS
>
> arch/arm/kvm/arm.c | 5 +-
> include/kvm/arm_vgic.h | 49 ++++-----
> virt/kvm/arm/vgic.c | 263 ++++++++++++++++++++++++++++++++++++++++---------
> 3 files changed, 249 insertions(+), 68 deletions(-)
>
> --
> 1.8.2.3
>
>
--
Christoffer
prev parent reply other threads:[~2013-10-21 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 12:16 [RFC PATCH 0/5] arm/arm64: KVM: dynamic VGIC sizing Marc Zyngier
2013-10-04 12:16 ` [RFC PATCH 1/5] arm/arm64: KVM: vgic: switch to dynamic allocation Marc Zyngier
2013-10-21 14:03 ` Christoffer Dall
2013-10-04 12:16 ` [RFC PATCH 2/5] arm/arm64: KVM: vgic: kill VGIC_NR_SHARED_IRQS Marc Zyngier
2013-10-21 14:03 ` Christoffer Dall
2013-10-04 12:16 ` [RFC PATCH 3/5] arm/arm64: KVM: vgic: kill VGIC_MAX_CPUS Marc Zyngier
2013-10-21 14:03 ` Christoffer Dall
2013-10-04 12:16 ` [RFC PATCH 4/5] arm/arm64: KVM: vgic: handle out-of-range MMIO accesses Marc Zyngier
2013-10-21 14:03 ` Christoffer Dall
2013-10-04 12:16 ` [RFC PATCH 5/5] arm/arm64: KVM: vgic: kill VGIC_NR_IRQS Marc Zyngier
2013-10-21 14:04 ` Christoffer Dall
2013-10-21 14:02 ` Christoffer Dall [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=20131021140251.GD39411@lvm \
--to=christoffer.dall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).