Re: [Xen-devel] Xen GCC coverage ARM64 testing - Unexpected Trap: Data Abort

[Viktor Mitin <viktor.mitin.19@xxxxxxxxx>]

Adding Xen maintainers to this email CC.

Thanks

On Thu, May 2, 2019 at 5:08 PM Viktor Mitin <viktor.mitin.19@xxxxxxxxx> wrote:
>
> Hi All,
>
> Please be aware that we have tried Xen ARM64 build with
> CONFIG_COVERAGE feature enabled. The build environment is next:
> Xen Versions tested: xen-4.12-stable, xen-4.13-staging
> Board: H3ULCB, R-Car H3 Ver.2.0
> Poky: Yocto Project Reference Distro 2.4.2
> Compiler: aarch64-poky-linux-gcc (Linaro GCC 7.2-2017.11) 7.2.1
>
> Both Xen versions (4.12 and staging) return "Unexpected Trap: Data
> Abort" issue in case of 'xencov reset' or 'xencov read' calls:
>
> root@h3ulcb:~# xencov reset
> (XEN) Data Abort Trap. Syndrome=0x7
> (XEN) Walking Hypervisor VA 0x361700 on CPU3 via TTBR 0x0000000078266000
> (XEN) 0TH[0x0] = 0x0000000078265f7f
> (XEN) 1ST[0x0] = 0x0000000078262f7f
> (XEN) 2ND[0x1] = 0x004000007825ff7f
> (XEN) 3RD[0x161] = 0x00600000781e1f7e
> (XEN) CPU3: Unexpected Trap: Data Abort
>
> Attaching the next log files (zipped in
> xen_with_config_coverage_logs.zip) with the details:
> - all the run-time exception details (rcarh3_config_coverage_trap.log);
> - xen package build log file with compilation options (compilation.log);
> - xen hypervisor .config file used for the build (xen_dot_config.log);
>
> Please share any comments or ideas about the issue.
>
> Thanks,
> Viktor Mitin

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel