All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 0/3] qtest: Remove 256 IRQ limit on irq intercepts
Date: Tue, 27 Oct 2026 09:30:41 -0300	[thread overview]
Message-ID: <87ld7jjpfy.fsf@suse.de> (raw)
In-Reply-To: <20261026125655.2668658-1-peter.maydell@linaro.org>

Peter Maydell <peter.maydell@linaro.org> writes:

> Currently both system/qtest.c and libqtest have a 256 IRQ limit
> on the size of an irq_intercept_in. If you try it with more then
> qtest.c will overrun its array, and libqtest will trip an assert.
> We have some real devices in board models that use more inbound
> IRQs than this (e.g. the GIC in the Arm virt board).
>
> This series removes both the fixed-sized arrays, so there's
> no artificial limit on how many GPIO lines we can cope with.
> I also fix in patch 2 a bug I noticed while doing this, where
> we don't check the GPIO group name for irq_intercept_in, so
> we apply the intercept to every input GPIO group the device
> has rather than only to the unnamed GPIO inputs.
>
> I haven't bothered to cc:stable on these because we don't
> trip over the limit for any of our existing qtests, though
> I don't anticipate there being any issues with the backport.
>
> thanks
> -- PMM
>
> Peter Maydell (3):
>   system/qtest: Avoid fixed-size irq_levels array for IRQ intercept
>   system/qtest: Check ngl->name for irq_intercept_in
>   tests/qtest/libqtest: Use a GArray for QTestState::irq_level[]
>
>  system/qtest.c         | 47 +++++++++++++++++++++++++++++-------------
>  tests/qtest/libqtest.c | 28 ++++++++++++-------------
>  2 files changed, 47 insertions(+), 28 deletions(-)

Queued, thanks.


      parent reply	other threads:[~2026-10-27 12:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 12:56 [PATCH 0/3] qtest: Remove 256 IRQ limit on irq intercepts Peter Maydell
2026-10-26 12:56 ` [PATCH 1/3] system/qtest: Avoid fixed-size irq_levels array for IRQ intercept Peter Maydell
2026-10-27 12:21   ` Fabiano Rosas
2026-10-26 12:56 ` [PATCH 2/3] system/qtest: Check ngl->name for irq_intercept_in Peter Maydell
2026-10-27 12:24   ` Fabiano Rosas
2026-10-26 12:56 ` [PATCH 3/3] tests/qtest/libqtest: Use a GArray for QTestState::irq_level[] Peter Maydell
2026-10-27 12:30   ` Fabiano Rosas
2026-10-27 12:30 ` Fabiano Rosas [this message]

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=87ld7jjpfy.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.