From: "Björn Töpel" <bjorn@kernel.org>
To: Anup Patel <apatel@ventanamicro.com>
Cc: "Anup Patel" <anup@brainfault.org>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
x86@kernel.org
Subject: Re: [RFC PATCH] genirq/matrix: Dynamic bitmap allocation
Date: Thu, 26 Oct 2023 19:26:38 +0200 [thread overview]
Message-ID: <87a5s5z44x.fsf@all.your.base.are.belong.to.us> (raw)
In-Reply-To: <CAK9=C2Vcbq_ReGcK51uOYp+M2hakz=9=RNHaHFMbfxhth_4cnA@mail.gmail.com>
Anup Patel <apatel@ventanamicro.com> writes:
> On Thu, Oct 26, 2023 at 3:50 PM Björn Töpel <bjorn@kernel.org> wrote:
>>
>> From: Björn Töpel <bjorn@rivosinc.com>
>>
>> Some (future) users of the irq matrix allocator, do not know the size
>> of the matrix bitmaps at compile time.
>>
>> To avoid wasting memory on unnecessary large bitmaps, size the bitmap
>> at matrix allocation time.
>>
>> Signed-off-by: Björn Töpel <bjorn@rivosinc.com>
>> ---
>> Here's a cleaned up, boot tested, proper patch.
>>
>> Thomas, this is just FYI/RFC. This change would only make sense, if
>> the RISC-V AIA series starts using the IRQ matrix allocator.
>
> I have dropped "multi-MSI" support from the AIA v12 series
> and also integrated the IRQ matrix allocator. This patch is
> included in the AIA v12 series.
Ok!
> For reference, look at riscv_aia_v12 branch at:
> https://github.com/avpatel/linux.git
>
> I still need to rebase this upon device MSI domain support
> from Thomas.
Note that the per-device domain support is already upstream, it's only
the ARM cleanups that are not.
IOW, there's no need to wait for the ARM cleanups. :-)
Björn
next prev parent reply other threads:[~2023-10-26 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 10:19 Björn Töpel
2023-10-26 10:41 ` Thomas Gleixner
2023-10-26 12:26 ` Anup Patel
2023-10-26 17:26 ` Björn Töpel [this message]
2023-10-26 23:17 ` Thomas Gleixner
2023-10-27 4:31 ` Anup Patel
2023-10-27 9:08 ` Thomas Gleixner
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=87a5s5z44x.fsf@all.your.base.are.belong.to.us \
--to=bjorn@kernel.org \
--cc=anup@brainfault.org \
--cc=apatel@ventanamicro.com \
--cc=bjorn@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®