From: Christoffer Dall <christoffer.dall@linaro.org>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Pavel Fedin <p.fedin@samsung.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Marc Zyngier <Marc.Zyngier@arm.com>
Subject: Re: [PATCH 1/2] KVM: arm/arm64: Optimize away redundant LR tracking
Date: Tue, 13 Oct 2015 17:41:22 +0200 [thread overview]
Message-ID: <20151013154122.GD21861@cbox> (raw)
In-Reply-To: <561BE62E.5050103@arm.com>
On Mon, Oct 12, 2015 at 05:56:14PM +0100, Andre Przywara wrote:
> Hi,
>
> On 02/10/15 15:44, Pavel Fedin wrote:
> > Currently we use vgic_irq_lr_map in order to track which LRs hold which
> > IRQs, and lr_used bitmap in order to track which LRs are used or free.
> >
> > vgic_irq_lr_map is actually used only for piggy-back optimization, and
> > can be easily replaced by iteration over lr_used. This is good because in
> > future, when LPI support is introduced, number of IRQs will grow up to at
> > least 16384, while numbers from 1024 to 8192 are never going to be used.
> > This would be a huge memory waste.
> >
> > In its turn, lr_used is also completely redundant since
> > ae705930fca6322600690df9dc1c7d0516145a93 ("arm/arm64: KVM: Keep elrsr/aisr
> > in sync with software model"), because together with lr_used we also update
> > elrsr. This allows to easily replace lr_used with elrsr, inverting all
> > conditions (because in elrsr '1' means 'free').
>
> So this looks pretty good to me, probably a better (because less
> intrusive) solution than my first two patches of the ITS emulation,
> which have a very similar scope.
> I will give this some testing on my boxes here to spot any regressions,
> but I guess I will use these two patches as the base for my next version
> of the ITS emulation series.
>
> Christoffer, Marc, do you consider these for 4.4 (since they are an
> independent cleanup) or do you want them to be part of the ITS emulation
> series since they make more sense in there?
>
I'll try to have a look at these tomorrow and I'll think about how to
merge this after I've looked at them.
Did you review these to the point where you can give your r-b tag here?
Thanks,
-Christoffer
next prev parent reply other threads:[~2015-10-13 15:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 14:44 [PATCH 0/2] KVM: arm/arm64: Clean up some obsolete code Pavel Fedin
2015-10-02 14:44 ` [PATCH 1/2] KVM: arm/arm64: Optimize away redundant LR tracking Pavel Fedin
2015-10-12 16:56 ` Andre Przywara
2015-10-13 15:41 ` Christoffer Dall [this message]
2015-10-22 21:42 ` Christoffer Dall
2015-10-23 7:12 ` Pavel Fedin
2015-10-02 14:44 ` [PATCH 2/2] KVM: arm/arm64: Merge vgic_set_lr() and vgic_sync_lr_elrsr() Pavel Fedin
2015-10-22 21:54 ` Christoffer Dall
2015-10-08 10:14 ` [PATCH 0/2] KVM: arm/arm64: Clean up some obsolete code Christoffer Dall
2015-10-08 10:55 ` Pavel Fedin
2015-10-08 10:56 ` Marc Zyngier
2015-10-08 11:15 ` Andre Przywara
2015-10-08 12:04 ` Pavel Fedin
2015-10-08 12:33 ` Christoffer Dall
2015-10-08 11:36 ` Pavel Fedin
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=20151013154122.GD21861@cbox \
--to=christoffer.dall@linaro.org \
--cc=Marc.Zyngier@arm.com \
--cc=andre.przywara@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=p.fedin@samsung.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).