* arm64 build failure on kvm/next
@ 2022-10-04 21:02 ` Oliver Upton
0 siblings, 0 replies; 4+ messages in thread
From: Oliver Upton @ 2022-10-04 21:02 UTC (permalink / raw)
To: pbonzini; +Cc: kvmarm, maz, kvmarm, kvm
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
--
Thanks,
Oliver
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
^ permalink raw reply [flat|nested] 4+ messages in thread* arm64 build failure on kvm/next
@ 2022-10-04 21:02 ` Oliver Upton
0 siblings, 0 replies; 4+ messages in thread
From: Oliver Upton @ 2022-10-04 21:02 UTC (permalink / raw)
To: pbonzini; +Cc: maz, seanjc, kvm, kvmarm, kvmarm
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
--
Thanks,
Oliver
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: arm64 build failure on kvm/next
@ 2022-10-04 22:32 ` Marc Zyngier
0 siblings, 0 replies; 4+ messages in thread
From: Marc Zyngier @ 2022-10-04 22:32 UTC (permalink / raw)
To: Oliver Upton; +Cc: kvmarm, pbonzini, kvmarm, kvm
On Tue, 04 Oct 2022 22:02:40 +0100,
Oliver Upton <oliver.upton@linux.dev> 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@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: arm64 build failure on kvm/next
@ 2022-10-04 22:32 ` Marc Zyngier
0 siblings, 0 replies; 4+ messages in thread
From: Marc Zyngier @ 2022-10-04 22:32 UTC (permalink / raw)
To: Oliver Upton; +Cc: pbonzini, seanjc, kvm, kvmarm, kvmarm
On Tue, 04 Oct 2022 22:02:40 +0100,
Oliver Upton <oliver.upton@linux.dev> 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.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-10-04 22:33 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2022-10-04 21:02 arm64 build failure on kvm/next Oliver Upton
2022-10-04 21:02 ` Oliver Upton
2022-10-04 22:32 ` Marc Zyngier
2022-10-04 22:32 ` Marc Zyngier
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.