[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAAhSdy2a6gs8o50afS_EpncinQvdUu--=a1PP5XfY8ZcJkWS2g@mail.gmail.com>
Date: Thu, 27 Dec 2018 10:57:33 +0530
From: Anup Patel <anup@...infault.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: Palmer Dabbelt <palmer@...ive.com>,
Albert Ou <aou@...s.berkeley.edu>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Jason Cooper <jason@...edaemon.net>,
Marc Zyngier <marc.zyngier@....com>,
Atish Patra <atish.patra@....com>,
linux-riscv@...ts.infradead.org,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 3/6] irqchip: sifive-plic: More flexible plic_irq_toggle()
On Wed, Dec 19, 2018 at 9:58 PM Christoph Hellwig <hch@...radead.org> wrote:
>
> On Tue, Dec 18, 2018 at 02:20:10PM +0530, Anup Patel wrote:
> > Actually these functions should not be inline because plic_toggle() uses
> > raw_spin_lock() and plic_irq_toggle() uses for-loop.
>
> So? It still inlines the all of two instances into each caller
> for slightly different but related work. Not sure it is 100% worth
> it, but probably more than the one to move the calculations to init
> time..
Not just at init time but these functions will also be used when
irq_affinity is changed by IRQ balancer at runtime.
Regards,
Anup
Powered by blists - more mailing lists