kvmarm.lists.cs.columbia.edu archive mirror
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org,
	Marc Zyngier <maz@kernel.org>, Will Deacon <will@kernel.org>,
	kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org
Subject: Re: REGRESSION: Upgrading host kernel from 5.11 to 5.13 breaks QEMU guests - perf/fw_devlink/kvm
Date: Mon, 20 Sep 2021 16:39:24 +0200	[thread overview]
Message-ID: <20210920143924.zh3zb7gf7wmd2uyx@gator> (raw)
In-Reply-To: <YUhYNnwaTt+5oMzh@shell.armlinux.org.uk>

On Mon, Sep 20, 2021 at 10:45:26AM +0100, Russell King (Oracle) wrote:
> On Sun, Sep 19, 2021 at 02:36:46PM +0100, Marc Zyngier wrote:
> > Urgh. That's a bummer. T1he PMU driver only comes up once it has found
> > its interrupt controller, which on the Armada 8040 is not the GIC, but
> > some weird thing on the side that doesn't actually serve any real
> > purpose. On HW where the PMU is directly wired into the GIC, it all
> > works fine, though by luck rather than by design.
> > 
> > Anyway, rant over. This is a bug that needs addressing so that KVM can
> > initialise correctly irrespective of the probing order. This probably
> > means that the static key controlling KVM's behaviour wrt the PMU must
> > be controlled by the PMU infrastructure itself, rather than KVM trying
> > to probe for it.
> > 
> > Can you please give the following hack a go (on top of 5.15-rc1)? I've
> > briefly tested it on my McBin, and it did the trick. I've also tested
> > it on the M1 (which really doesn't have an architectural PMU) to
> > verify that it was correctly failing.
> 
> My test program that derives the number of registers qemu uses now
> reports 236 registers again and I see:

Hi Russell,

You may be interested in kvm selftests and this one[1] in particular.

[1] tools/testing/selftests/kvm/aarch64/get-reg-list.c

Thanks,
drew


> 
> kvm [7]: PMU detected and enabled
> 
> in the kernel boot log.
> 
> Tested-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>
> 
> Thanks.
> 
> -- 
> RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
> FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
> _______________________________________________
> kvmarm mailing list
> kvmarm@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
> 

_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

  reply	other threads:[~2021-09-20 14:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 16:17 REGRESSION: Upgrading host kernel from 5.11 to 5.13 breaks QEMU guests - perf/fw_devlink/kvm Russell King (Oracle)
2021-09-19 13:36 ` Marc Zyngier
2021-09-20  9:45   ` Russell King (Oracle)
2021-09-20 14:39     ` Andrew Jones [this message]
2021-09-20  9:56   ` Will Deacon
2021-09-20 10:23     ` Marc Zyngier

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=20210920143924.zh3zb7gf7wmd2uyx@gator \
    --to=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=maz@kernel.org \
    --cc=will@kernel.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).