On Tue, 04 Oct 2022 22:02:40 +0100, Oliver Upton <oliver.upton@xxxxxxxxx> wrote: > > Hey Paolo, > > Just wanted to give you a heads up about a build failure on kvm/next. > Marc pulled some of the sysreg refactoring updates from core arm64 to > resolve a conflict, which resulted in: > > drivers/perf/arm_spe_pmu.c:677:7: error: use of undeclared identifier 'ID_AA64DFR0_PMSVER_8_2' > case ID_AA64DFR0_PMSVER_8_2: > ^ > drivers/perf/arm_spe_pmu.c:679:7: error: use of undeclared identifier 'ID_AA64DFR0_PMSVER_8_3' > case ID_AA64DFR0_PMSVER_8_3: > ^ > drivers/perf/arm_spe_pmu.c:961:10: error: use of undeclared identifier 'ID_AA64DFR0_PMSVER_SHIFT' > ID_AA64DFR0_PMSVER_SHIFT); > > The fix has since gone in on the arm64 side [1], in case you want to > mention in your pull request. > > [1]: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/?h=for-next/sysreg&id=db74cd6337d2691ea932e36b84683090f0712ec1 Also worth noting that the SPE driver is not part of defconfig, which is probably why it wasn't spotted the first place. Anyway, odds are that the arm64 pull-request will get in before the KVM one, making this pretty much invisible... M. -- Without deviation from the norm, progress is not possible. _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
