On Mon, May 13, 2019 at 05:39:55PM +0300, Viktor Mitin wrote:
> Hi Wei and Julien,
>
> Thank you for the hints provided. It is appeared that it was Yocto Xen
> receipt issue and not Xen coverage feature issue.
> We see that xencov* tools are built anyway, even in the case when
> CONFIG_COVERAGE is
Hi,
On 5/13/19 3:39 PM, Viktor Mitin wrote:
Hi Wei and Julien,
---
Xen 4.13 has not been checked yet with the patch. Currently, xen 4.13
staging fails to boot due to unknown reason... it worked some days
ago.
It hangs after the next log currently:
(XEN) Failed to bring up CPU 7 (error -5)
(XEN)
Hi Wei and Julien,
Thank you for the hints provided. It is appeared that it was Yocto Xen
receipt issue and not Xen coverage feature issue.
We see that xencov* tools are built anyway, even in the case when
CONFIG_COVERAGE is not enabled in hypervisor Kconfig.
Is there a reason for this?
To summar
On Mon, May 13, 2019 at 01:29:12PM +0300, Viktor Mitin wrote:
> > > aarch64-poky-linux-gcc -DBUILD_ID -fno-strict-aliasing -std=gnu99
> > > -Wall -Wstrict-prototypes -Wdeclaration-after-statement
> > > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -O2
> > > -fomit-frame-pointer
> > >
On 5/13/19 11:29 AM, Viktor Mitin wrote:
aarch64-poky-linux-gcc -DBUILD_ID -fno-strict-aliasing -std=gnu99
-Wall -Wstrict-prototypes -Wdeclaration-after-statement
-Wno-unused-but-set-variable -Wno-unused-local-typedefs -O2
-fomit-frame-pointer
-D__XEN_INTERFACE_VERSION__=__XEN_LATEST_INTERF
> > aarch64-poky-linux-gcc -DBUILD_ID -fno-strict-aliasing -std=gnu99
> > -Wall -Wstrict-prototypes -Wdeclaration-after-statement
> > -Wno-unused-but-set-variable -Wno-unused-local-typedefs -O2
> > -fomit-frame-pointer
> > -D__XEN_INTERFACE_VERSION__=__XEN_LATEST_INTERFACE_VERSION__ -MMD -MF
>
On 5/13/19 9:18 AM, Viktor Mitin wrote:
Hi Julien,
Hi,
Please be aware that the patch you proposed (+nocov-y += libfdt.o)
failed to build with the next error (xen 4.12):
My patch is based on 4.13, although should work on Xen 4.12. But...
aarch64-poky-linux-gcc -DBUILD_ID -fno-strict-
Hi Julien,
Please be aware that the patch you proposed (+nocov-y += libfdt.o)
failed to build with the next error (xen 4.12):
aarch64-poky-linux-gcc -DBUILD_ID -fno-strict-aliasing -std=gnu99
-Wall -Wstrict-prototypes -Wdeclaration-after-statement
-Wno-unused-but-set-variable -Wno-unused-local-
On Fri, May 03, 2019 at 03:16:52PM +0100, Julien Grall wrote:
> > > diff --git a/xen/common/libfdt/Makefile b/xen/common/libfdt/Makefile
> > > index d81f54b6b8..c075bbf546 100644
> > > --- a/xen/common/libfdt/Makefile
> > > +++ b/xen/common/libfdt/Makefile
> > > @@ -3,6 +3,7 @@ include Makefile.lib
Hi,
On 03/05/2019 14:41, Wei Liu wrote:
On Fri, May 03, 2019 at 02:35:08PM +0100, Julien Grall wrote:
Hi Wei,
On 5/3/19 12:08 PM, Wei Liu wrote:
On Thu, May 02, 2019 at 09:43:17PM +0100, Julien Grall wrote:
(+ Wei)
On 5/2/19 5:55 PM, Viktor Mitin wrote:
Hi Julien,
Hi,
Please find trace
On Fri, May 03, 2019 at 02:35:08PM +0100, Julien Grall wrote:
> Hi Wei,
>
> On 5/3/19 12:08 PM, Wei Liu wrote:
> > On Thu, May 02, 2019 at 09:43:17PM +0100, Julien Grall wrote:
> > > (+ Wei)
> > >
> > > On 5/2/19 5:55 PM, Viktor Mitin wrote:
> > > > Hi Julien,
> > >
> > > Hi,
> > >
> > > > Plea
Hi Wei,
On 5/3/19 12:08 PM, Wei Liu wrote:
On Thu, May 02, 2019 at 09:43:17PM +0100, Julien Grall wrote:
(+ Wei)
On 5/2/19 5:55 PM, Viktor Mitin wrote:
Hi Julien,
Hi,
Please find trace log below:
root@h3ulcb:~# xencov reset
(XEN) Data Abort Trap. Syndrome=0x7
(XEN) Walking Hypervisor VA
On Thu, May 02, 2019 at 09:43:17PM +0100, Julien Grall wrote:
> (+ Wei)
>
> On 5/2/19 5:55 PM, Viktor Mitin wrote:
> > Hi Julien,
>
> Hi,
>
> > Please find trace log below:
> >
> > root@h3ulcb:~# xencov reset
> > (XEN) Data Abort Trap. Syndrome=0x7
> > (XEN) Walking Hypervisor VA 0x361700 on CP
(+ Wei)
On 5/2/19 5:55 PM, Viktor Mitin wrote:
Hi Julien,
Hi,
Please find trace log below:
root@h3ulcb:~# xencov reset
(XEN) Data Abort Trap. Syndrome=0x7
(XEN) Walking Hypervisor VA 0x361700 on CPU3 via TTBR 0x78266000
So this is a data abort when trying to access VA 0x361700 (it i
Hi Julien,
Please find trace log below:
root@h3ulcb:~# xencov reset
(XEN) Data Abort Trap. Syndrome=0x7
(XEN) Walking Hypervisor VA 0x361700 on CPU3 via TTBR 0x78266000
(XEN) 0TH[0x0] = 0x78265f7f
(XEN) 1ST[0x0] = 0x78262f7f
(XEN) 2ND[0x1] = 0x00407825ff7f
(XEN) 3RD[0x
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 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:
Adding Xen maintainers to this email CC.
Thanks
On Thu, May 2, 2019 at 5:08 PM Viktor Mitin 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
>
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
18 matches
Mail list logo
