From: Roque Arcudia Hernandez <roqueh@google.com>
To: qemu-devel@nongnu.org
Subject: Hard limit on 256 IRQs in qtest
Date: Thu, 21 Jul 2022 09:17:13 -0700 [thread overview]
Message-ID: <CAKbPEtZxCGfz4_h8_YMg2bb-kQF0sorLAppKcBTweV0gxM+OLA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 615 bytes --]
Hello,
To write a qtest for an SoC using ARM GICv3 as interrupt controller the
qtest infrastructure is short on IRQs.
File tests/qtest/libqtest.c defines:
#define MAX_IRQ 256
Which is the number of elements in the array that is used to keep track of
the value of the irq gpio:
bool irq_level[MAX_IRQ];
The GICv3 can take up to 1020. The SoC we are trying to emulate uses more
than the current 256 limit we can observe at the GIC input. If we focus
just on the external interrupt range the GIC would need 1020 - 32 = 988
IRQs. Will it be OK to make this change to the qtest infrastructure?
Thanks,
Roque
[-- Attachment #2: Type: text/html, Size: 3292 bytes --]
next reply other threads:[~2022-07-21 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 16:17 Roque Arcudia Hernandez [this message]
2022-07-22 9:26 ` Hard limit on 256 IRQs in qtest Thomas Huth
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=CAKbPEtZxCGfz4_h8_YMg2bb-kQF0sorLAppKcBTweV0gxM+OLA@mail.gmail.com \
--to=roqueh@google.com \
--cc=qemu-devel@nongnu.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).