From: Andrew Jones <andrew.jones@linux.dev>
To: Nadav Amit <nadav.amit@gmail.com>
Cc: kvmarm@lists.linux.dev, kvmarm@lists.cs.columbia.edu,
kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH] arm64: timer: ignore ISTATUS with disabled timer
Date: Wed, 28 Jun 2023 13:40:24 +0200 [thread overview]
Message-ID: <20230628-1a712a9e7c4710acaa744f52@orel> (raw)
In-Reply-To: <20230615003832.161134-1-namit@vmware.com>
On Wed, Jun 14, 2023 at 05:38:32PM -0700, Nadav Amit wrote:
> From: Nadav Amit <nadav.amit@gmail.com>
>
> According to ARM specifications for the vtimer (CNTV_CTL_EL0): "When the
> value of the ENABLE bit is 0, the ISTATUS field is UNKNOWN."
>
> Currently the test, however, does check that ISTATUS is cleared when the
> ENABLE bit is zero. Remove this check as the value is unknown.
Hmm, does it? timer_pending() is
/* Check that the timer condition is met. */
static bool timer_pending(struct timer_info *info)
{
return (info->read_ctl() & ARCH_TIMER_CTL_ENABLE) &&
(info->read_ctl() & ARCH_TIMER_CTL_ISTATUS);
}
which I would expect to short-circuit when ENABLE is zero.
Thanks,
drew
>
> Signed-off-by: Nadav Amit <nadav.amit@gmail.com>
> ---
> arm/timer.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arm/timer.c b/arm/timer.c
> index 2cb8051..0b976a7 100644
> --- a/arm/timer.c
> +++ b/arm/timer.c
> @@ -256,7 +256,7 @@ static void test_timer_pending(struct timer_info *info)
> set_timer_irq_enabled(info, true);
>
> report(!info->irq_received, "no interrupt when timer is disabled");
> - report(!timer_pending(info) && gic_timer_check_state(info, GIC_IRQ_STATE_INACTIVE),
> + report(gic_timer_check_state(info, GIC_IRQ_STATE_INACTIVE),
> "interrupt signal no longer pending");
>
> info->write_cval(now - 1);
> --
> 2.34.1
>
next prev parent reply other threads:[~2023-06-28 11:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 0:38 [kvm-unit-tests PATCH] arm64: timer: ignore ISTATUS with disabled timer Nadav Amit
2023-06-28 11:40 ` Andrew Jones [this message]
2023-07-01 17:26 ` Nadav Amit
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=20230628-1a712a9e7c4710acaa744f52@orel \
--to=andrew.jones@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=nadav.amit@gmail.com \
/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