qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: Gustavo Romero <gustavo.romero@linaro.org>, qemu-devel@nongnu.org
Cc: lvivier@redhat.com, pbonzini@redhat.com, philmd@linaro.org
Subject: Re: [PATCH] test/qtest: Add an API function to capture IRQ toggling
Date: Mon, 13 Nov 2023 07:59:21 +0100	[thread overview]
Message-ID: <ddb3f1c5-28d1-472d-b491-703a3e1c6711@redhat.com> (raw)
In-Reply-To: <20231112013801.293970-1-gustavo.romero@linaro.org>

On 12/11/2023 02.38, Gustavo Romero wrote:
> Currently the QTest API does not provide a function to allow capturing
> when an IRQ line is toggled (raised then lowered). Functions like
> qtest_get_irq() read the current state of the intercepted IRQ lines,
> which is already low when the function is called, since the line is
> toggled.
> 
> This commit introduces a new function, qtest_get_irq_trigger_counter(),
> which returns the number of times a given intercepted IRQ line was
> triggered (raised), hence allowing to capture when an IRQ line was
> toggled.
> 
> Signed-off-by: Gustavo Romero <gustavo.romero@linaro.org>
> ---
>   tests/qtest/libqtest.c | 12 ++++++++++++
>   tests/qtest/libqtest.h |  9 +++++++++
>   2 files changed, 21 insertions(+)
> 
> diff --git a/tests/qtest/libqtest.c b/tests/qtest/libqtest.c
> index f33a210861..21891b52f1 100644
> --- a/tests/qtest/libqtest.c
> +++ b/tests/qtest/libqtest.c
> @@ -82,6 +82,7 @@ struct QTestState
>       int expected_status;
>       bool big_endian;
>       bool irq_level[MAX_IRQ];
> +    uint64_t irq_trigger_counter[MAX_IRQ];
>       GString *rx;
>       QTestTransportOps ops;
>       GList *pending_events;
> @@ -498,6 +499,7 @@ static QTestState *qtest_init_internal(const char *qemu_bin,
>       s->rx = g_string_new("");
>       for (i = 0; i < MAX_IRQ; i++) {
>           s->irq_level[i] = false;
> +        s->irq_trigger_counter[i] = 0;
>       }
>   
>       /*
> @@ -690,6 +692,7 @@ redo:
>   
>           if (strcmp(words[1], "raise") == 0) {
>               s->irq_level[irq] = true;
> +            s->irq_trigger_counter[irq]++;

Not sure whether you can get some "raise" events in a row without some 
"lower" events in between ... but just in case, I wonder whether it would 
make sense to check whether it is really a rising edge, i.e.:

            if (strcmp(words[1], "raise") == 0) {
                if (!s->irq_level[irq]) {
                    s->irq_trigger_counter[irq]++;
                }
                s->irq_level[irq] = true;

What do you think?

>           } else {
>               s->irq_level[irq] = false;
>           }

Anyway:
Acked-by: Thomas Huth <thuth@redhat.com>



  reply	other threads:[~2023-11-13  7:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12  1:38 [PATCH] test/qtest: Add an API function to capture IRQ toggling Gustavo Romero
2023-11-13  6:59 ` Thomas Huth [this message]
2023-11-13 10:14   ` Philippe Mathieu-Daudé
2023-11-13 17:33     ` Gustavo Romero
2023-12-13  9:15       ` Philippe Mathieu-Daudé
2024-02-21 15:47         ` Gustavo Romero

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=ddb3f1c5-28d1-472d-b491-703a3e1c6711@redhat.com \
    --to=thuth@redhat.com \
    --cc=gustavo.romero@linaro.org \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@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 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).