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

[Julien Grall <julien.grall@xxxxxxx>]

Hi,

On 5/2/19 3:50 PM, Viktor Mitin wrote:
> 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
Per the value, the syndrome is invalid. As I will not open a zip (see 
below why), could you post the full stack trace?
> > (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:
Please don't send a 54KB attachment on the mailing list. This is using 
up space for every one on the ML. Instead you should upload somewhere 
(e.g pastebin).
But I am afraid, I am not going to open any archive sent on the mailing 
list. Please upload file separately. However....
> > - all the run-time exception details (rcarh3_config_coverage_trap.log);
> > - xen package build log file with compilation options (compilation.log);
This is not necessary.

> > - xen hypervisor .config file used for the build (xen_dot_config.log);
> >
> > Please share any comments or ideas about the issue.
GCOV on Arm has never been tested. So it might be possible there might 
be some issues with it.
Cheers,

--
Julien Grall

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