Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Nadav Amit <nadav.amit@gmail.com>
To: Andrew Jones <andrew.jones@linux.dev>
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: Sat, 1 Jul 2023 10:26:18 -0700	[thread overview]
Message-ID: <BC525FC4-B2DE-4FA4-B4E4-FF4206F5D59F@gmail.com> (raw)
In-Reply-To: <20230628-1a712a9e7c4710acaa744f52@orel>



> On Jun 28, 2023, at 4:40 AM, Andrew Jones <andrew.jones@linux.dev> wrote:
> 
> 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.

Yes, my bad. Drop it.

I had a different unrelated interrupt before that turned on the ENABLE.
This just mask an additional failure.

Obviously we can reset the ENABLE before each test, but I presume it is
fair to say that in general if a certain test fails, subsequent failures
are prone to be false-positives.



      reply	other threads:[~2023-07-01 17:26 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
2023-07-01 17:26   ` Nadav Amit [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=BC525FC4-B2DE-4FA4-B4E4-FF4206F5D59F@gmail.com \
    --to=nadav.amit@gmail.com \
    --cc=andrew.jones@linux.dev \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=kvmarm@lists.linux.dev \
    /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