Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Andrew Jones <andrew.jones@linux.dev>
Cc: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu
Subject: Re: [kvm-unit-tests PATCH v4 0/4] arm: pmu: Fixes for bare metal
Date: Fri, 28 Oct 2022 16:01:50 +0100	[thread overview]
Message-ID: <86fsf8dmap.wl-maz@kernel.org> (raw)
In-Reply-To: <20221028114041.5symayccvdgkqaor@kamzik>

Hi Drew,

On Fri, 28 Oct 2022 12:40:41 +0100,
Andrew Jones <andrew.jones@linux.dev> wrote:
> 
> On Thu, Aug 11, 2022 at 11:52:06AM -0700, Ricardo Koller wrote:
> > There are some tests that fail when running on bare metal (including a
> > passthrough prototype).  There are three issues with the tests.  The
> > first one is that there are some missing isb()'s between enabling event
> > counting and the actual counting. This wasn't an issue on KVM as
> > trapping on registers served as context synchronization events. The
> > second issue is that some tests assume that registers reset to 0.  And
> > finally, the third issue is that overflowing the low counter of a
> > chained event sets the overflow flag in PMVOS and some tests fail by
> > checking for it not being set.
> > 
> > Addressed all comments from the previous version:
> > https://lore.kernel.org/kvmarm/YvPsBKGbHHQP+0oS@google.com/T/#mb077998e2eb9fb3e15930b3412fd7ba2fb4103ca
> > - add pmu_reset() for 32-bit arm [Andrew]
> > - collect r-b from Alexandru
> > 
> > Thanks!
> > Ricardo
> > 
> > Ricardo Koller (4):
> >   arm: pmu: Add missing isb()'s after sys register writing
> >   arm: pmu: Add reset_pmu() for 32-bit arm
> >   arm: pmu: Reset the pmu registers before starting some tests
> >   arm: pmu: Check for overflow in the low counter in chained counters
> >     tests
> > 
> >  arm/pmu.c | 72 ++++++++++++++++++++++++++++++++++++++++++-------------
> >  1 file changed, 55 insertions(+), 17 deletions(-)
> >
> 
> Hi all,
> 
> Please refresh my memory. Does this series work on current platforms? Or
> was it introducing new test failures which may be in the test, as opposed
> to KVM? If they work on most platforms, but not on every platform, then
> have we identified what triggers them to fail and whether that should be
> fixed or just worked-around? I'm sorry I still can't help out with the
> testing as I haven't yet had time to setup the Rpi that Mark Rutland gave
> me in Dublin.

This series does show that KVM is buggy, and I have patches out to fix
it [1]. The patches should work on anything, really.

> I know this series has been rotting on arm/queue for months, so I'll be
> happy to merge it if the consensus is to do so. I can also drop it, or
> some of the patches, if that's the consensus.

I'd be very happy to see these patches being merged.

Thanks,

	M.

[1] https://lore.kernel.org/r/20221028105402.2030192-1-maz@kernel.org

-- 
Without deviation from the norm, progress is not possible.
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

  reply	other threads:[~2022-10-28 15:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 18:52 [kvm-unit-tests PATCH v4 0/4] arm: pmu: Fixes for bare metal Ricardo Koller
2022-08-11 18:52 ` [kvm-unit-tests PATCH v4 1/4] arm: pmu: Add missing isb()'s after sys register writing Ricardo Koller
2022-08-11 18:52 ` [kvm-unit-tests PATCH v4 2/4] arm: pmu: Add reset_pmu() for 32-bit arm Ricardo Koller
2022-08-11 18:52 ` [kvm-unit-tests PATCH v4 3/4] arm: pmu: Reset the pmu registers before starting some tests Ricardo Koller
2022-08-11 18:52 ` [kvm-unit-tests PATCH v4 4/4] arm: pmu: Check for overflow in the low counter in chained counters tests Ricardo Koller
2022-08-12  6:33 ` [kvm-unit-tests PATCH v4 0/4] arm: pmu: Fixes for bare metal Andrew Jones
2022-08-12 17:57   ` Ricardo Koller
2022-08-13  8:13 ` Marc Zyngier
2022-10-28 11:40 ` Andrew Jones
2022-10-28 15:01   ` Marc Zyngier [this message]
2022-10-28 15:31     ` Andrew Jones

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=86fsf8dmap.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=andrew.jones@linux.dev \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    /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