Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
From:   Rasmus Villemoes <linux@rasmusvillemoes.dk>
To:     Marc Zyngier <marc.zyngier@arm.com>, linux-kernel@vger.kernel.org
Cc:     Rasmus Villemoes <linux@rasmusvillemoes.dk>, stable@vger.kernel.org
Subject: [PATCH 0/4] irqchip/gic-v3-its: free_lpi_range tweaks
Date:   Tue, 12 Mar 2019 18:33:45 +0100
Message-Id: <20190312173350.4025-1-linux@rasmusvillemoes.dk>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

I noticed that the O(n log n) behaviour of free_lpi_range could easily
be made O(n) (patch 4), though I don't suppose n is ever large enough
to actually matter. While there, I also stumbled on two other
micro-optimizations (2 and 3).

Then while writing the commit log for the last patch, I noticed that
the cmp callback I was removing was actually buggy, so I went back and
added a patch in front suitable for -stable. I'll leave it to others
to decide if it's important enough for that.

Please note that this is only compile-tested.

Rasmus Villemoes (4):
  irqchip/gic-v3-its: fix comparison logic in lpi_range_cmp
  irqchip/gic-v3-its: move allocation outside mutex
  irqchip/gic-v3-its: drop redundant initialization in mk_lpi_range
  irqchip/gic-v3-its: make free_lpi_range a little cheaper

 drivers/irqchip/irq-gic-v3-its.c | 75 +++++++++++++++-----------------
 1 file changed, 36 insertions(+), 39 deletions(-)

-- 
2.20.1