* [xen-unstable-smoke test] 114332: regressions - FAIL
@ 2017-10-11 7:17 osstest service owner
2017-10-11 7:30 ` Roger Pau Monné
0 siblings, 1 reply; 3+ messages in thread
From: osstest service owner @ 2017-10-11 7:17 UTC (permalink / raw)
To: xen-devel, osstest-admin
flight 114332 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/114332/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 7 xen-boot fail REGR. vs. 114299
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-check fail never pass
version targeted for testing:
xen f17d2cd2ffeda70aba8788910e9d088415562c8b
baseline version:
xen 3b40cfcd1a1912c2e4c4eb353dc77cbf35c63c3a
Last test of basis 114299 2017-10-10 21:02:54 Z 0 days
Failing since 114308 2017-10-10 23:01:10 Z 0 days 3 attempts
Testing same since 114318 2017-10-11 02:19:34 Z 0 days 2 attempts
------------------------------------------------------------
People who touched revisions under test:
Andre Przywara <andre.przywara@arm.com>
Julien Grall <julien.grall@arm.com>
Stefano Stabellini <sstabellini@kernel.org>
jobs:
build-amd64 pass
build-armhf pass
build-amd64-libvirt pass
test-armhf-armhf-xl fail
test-amd64-amd64-xl-qemuu-debianhvm-i386 pass
test-amd64-amd64-libvirt pass
------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images
Logs, config files, etc. are available at
http://logs.test-lab.xenproject.org/osstest/logs
Explanation of these reports, and of osstest in general, is at
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master
Test harness code can be found at
http://xenbits.xen.org/gitweb?p=osstest.git;a=summary
Not pushing.
------------------------------------------------------------
commit f17d2cd2ffeda70aba8788910e9d088415562c8b
Author: Andre Przywara <andre.przywara@arm.com>
Date: Sat Oct 7 01:06:40 2017 +0100
ARM: sunxi: support more Allwinner SoCs
So far we only supported the Allwinner A20 SoC. Add support for most
of the other virtualization capable Allwinner SoCs by:
- supporting the watchdog in newer (sun8i) SoCs
- getting the watchdog address from DT
- adding compatible strings for other 32-bit SoCs
- adding compatible strings for 64-bit SoCs
As all 64-bit SoCs support system reset via PSCI, we don't use the
platform specific reset routine there. Should the 32-bit SoCs start to
properly support the PSCI 0.2 SYSTEM_RESET call, we will use it for them
automatically, as we try PSCI first, then fall back to platform reset.
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
commit e2dfe4a037b0c6ccfd2375e4b60668109a0118e5
Author: Julien Grall <julien.grall@arm.com>
Date: Mon Oct 9 14:23:41 2017 +0100
xen/arm: mm: Use memory flags for modify_xen_mappings rather than custom one
This will help to consolidate the page-table code and avoid different
path depending on the action to perform.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
commit 6b88beed40c756aaff018d286f4de31351240a93
Author: Julien Grall <julien.grall@arm.com>
Date: Mon Oct 9 14:23:40 2017 +0100
xen/arm: mm: Handle permission flags when adding a new mapping
Currently, all the new mappings will be read-write non-executable. Allow the
caller to use other permissions.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
commit 28f2ad440a08908010abec43b7ccc3283051e943
Author: Julien Grall <julien.grall@arm.com>
Date: Mon Oct 9 14:23:39 2017 +0100
xen/arm: mm: Embed permission in the flags
Currently, it is not possible to specify the permission of a new
mapping. It would be necessary to use the function modify_xen_mappings
with a different set of flags.
Introduce a couple of new flags for the permissions (Non-eXecutable,
Read-Only) and also provides definition that combine the memory attribute
and permission for common combinations.
PAGE_HYPERVISOR is now an alias to PAGE_HYPERVISOR_RW (read-write,
non-executable mappings). This does not affect the current mapping using
PAGE_HYPERVISOR because Xen is currently forcing all the mapping to be
non-executable by default (see mfn_to_xen_entry).
A follow-up patch will change modify_xen_mappings to use the new flags.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Signed-off-by: Stefano Stabellini <sstabellini@kernel.org>
commit 5f3edb5f32e511b915d173403d0b7b5ea38e00ad
Author: Julien Grall <julien.grall@arm.com>
Date: Mon Oct 9 14:23:38 2017 +0100
xen/arm: page: Describe the layout of flags used to update page tables
Currently, the flags used to update page tables (i.e PAGE_HYPERVISOR_*)
only contains the memory attribute index. Follow-up patches will add
more information in it. So document the current layout.
At the same time introduce PAGE_AI_MASK to get the memory attribute
index easily.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
commit 7d68c8db25f0ffc7f39af2fc929f1c77c1affa01
Author: Julien Grall <julien.grall@arm.com>
Date: Mon Oct 9 14:23:37 2017 +0100
xen/arm: mm: Use PAGE_HYPERVISOR_* instead of MT_* when calling set_fixmap
At the moment, PAGE_HYPERVISOR_* and MT_* have exactly the same value.
In a follow-up patch the former will be extended to carry more
information.
It looks like the caller of set_fixmap are mixing the both. Stay
consistent and only use PAGE_HYPERVISOR_*. This is also match the
behavior of create_xen_entries and would potentially allow to share some
part in the future.
Also rename the parameter 'attributes' to 'flags' so it is clearer what
is the interface.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Acked-by: Stefano Stabellini <sstabellini@kernel.org>
commit b797f4d03bed21ff643a93909abdd58107b6c8cf
Author: Julien Grall <julien.grall@arm.com>
Date: Mon Oct 9 14:23:36 2017 +0100
xen/arm: mm: Rename 'ai' into 'flags' in create_xen_entries
The parameter 'ai' is used either for attribute index or for
permissions. Follow-up patch will rework that parameters to carry more
information. So rename the parameter to 'flags'.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
commit fc24d616beda7b0d9a96c588b06862f46b189181
Author: Julien Grall <julien.grall@arm.com>
Date: Mon Oct 9 14:23:35 2017 +0100
xen/arm: Switch to SYS_STATE_boot just after end_boot_allocator()
We should consider the early boot period to end when we stop using the
boot allocator. This is inline with x86 and will be helpful to know
whether we should allocate memory from the boot allocator or xenheap.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
commit 9a7f6dd6d2244993968569deb9963934add0a50d
Author: Julien Grall <julien.grall@arm.com>
Date: Mon Oct 9 14:23:34 2017 +0100
xen/arm: mm: Rename and clarify AP[1] in the stage-1 page table
The description of AP[1] in Xen is based on testing rather than the ARM
ARM.
Per the ARM ARM, on EL2 stage-1 page table, AP[1] is RES1 as the
translation regime applies to only one exception level (see D4.4.4 and
G4.6.1 in ARM DDI 0487B.a).
Update the comment and also rename the field to match the description in
the ARM ARM.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Acked-by: Stefano Stabellini <sstabellini@kernel.org>
commit a0543df403d457e139069d3356d42a89b25d11df
Author: Julien Grall <julien.grall@arm.com>
Date: Mon Oct 9 14:23:33 2017 +0100
xen/arm: page: Clean-up the definition of MAIRVAL
Currently MAIRVAL is defined in term of MAIR0VAL and MAIR1VAL which are
both hardcoded value. This makes quite difficult to understand the value
written in both registers.
Rework the definition by using value of each attribute shifted by their
associated index.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
commit 70a3bd02f963d60cab30a2d6e6589ac477132d7c
Author: Julien Grall <julien.grall@arm.com>
Date: Mon Oct 9 14:23:32 2017 +0100
xen/arm: page: Use ARMv8 naming to improve readability
This is based on the Linux ARMv8 naming scheme (see arch/arm64/mm/proc.S). Each
type will contain "NORMAL" or "DEVICE" to make clear whether each attribute
targets device or normal memory.
Signed-off-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
(qemu changes not included)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [xen-unstable-smoke test] 114332: regressions - FAIL
2017-10-11 7:17 [xen-unstable-smoke test] 114332: regressions - FAIL osstest service owner
@ 2017-10-11 7:30 ` Roger Pau Monné
2017-10-11 14:30 ` Julien Grall
0 siblings, 1 reply; 3+ messages in thread
From: Roger Pau Monné @ 2017-10-11 7:30 UTC (permalink / raw)
To: osstest service owner; +Cc: Julien Grall, xen-devel, Stefano Stabellini
Adding Julien and Stefano.
On Wed, Oct 11, 2017 at 07:17:59AM +0000, osstest service owner wrote:
> flight 114332 xen-unstable-smoke real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/114332/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-armhf-armhf-xl 7 xen-boot fail REGR. vs. 114299
Seems like Xen is not able to start on the Exynos or Cubietrucks
anymore:
Oct 11 06:52:11.479093 \rU-Boot 2014.10-00007-g0052a7d (Sep 29 2015 - 10:21:38) for ARNDALE
Oct 11 06:52:11.487075
Oct 11 06:52:11.487090 \rCPU: Exynos5250@1000MHz
Oct 11 06:52:11.487106
Oct 11 06:52:11.487118 \rBoard: Arndale
Oct 11 06:52:11.487132 \rI2C: i2c_init: failed to init bus 0 for speed = 100000
Oct 11 06:52:11.495063 \rready
Oct 11 06:52:11.495078 \rDRAM: 2 GiB
Oct 11 06:52:11.495092 \rtrace: copying 000ab188 bytes of early data from 50000000 to beff0000
Oct 11 06:52:11.511080 \rtrace: enabled
Oct 11 06:52:11.551032 \rMMC: EXYNOS DWMMC: 0, EXYNOS DWMMC: 1
Oct 11 06:52:11.911146 \ri2c_init: failed to init bus 0 for speed = 100000
Oct 11 06:52:11.967154 \rIn: serial
Oct 11 06:52:11.967185 \rOut: serial
Oct 11 06:52:11.967211 \rErr: serial
Oct 11 06:52:11.967236 \rSCSI: ARNDALE SCSI INIT
Oct 11 06:52:11.975119 \rTarget spinup took 0 ms.
Oct 11 06:52:11.983147 \rAHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode
Oct 11 06:52:11.983188 \rflags: ncq stag pm led clo only pmp pio slum part ccc apst
Oct 11 06:52:11.991155 \rNet: Net Initialization Skipped
Oct 11 06:52:11.991189 \rNo ethernet found.
Oct 11 06:52:11.991216 \rHostname: arndale-westfield
Oct 11 06:52:11.999141 \rHit any key to stop autoboot: 2 \b\b\b 1 \b\b\b 0
Oct 11 06:52:13.919168 \r(Re)start USB...
Oct 11 06:52:13.919223 \rUSB0: USB EHCI 1.00
Oct 11 06:52:13.927090 \rscanning bus 0 for devices... 4 USB Device(s) found
Oct 11 06:52:19.523158 \r scanning usb for storage devices... 0 Storage Device(s) found
Oct 11 06:52:19.531073 \r scanning usb for ethernet devices... 1 Ethernet Device(s) found
Oct 11 06:52:19.971149 \rWaiting for Ethernet connection... done.
Oct 11 06:52:21.571140 \rBOOTP broadcast 1
Oct 11 06:52:21.571189 \rBOOTP broadcast 2
Oct 11 06:52:22.619159 \rDHCP client bound to address 172.16.144.45 (1092 ms)
Oct 11 06:52:22.627153 \rUsing asx0 device
Oct 11 06:52:22.627188 \rTFTP from server 172.16.144.3; our IP address is 172.16.144.45
Oct 11 06:52:22.635136 \rFilename 'pxelinux.0'.
Oct 11 06:52:22.635157 \rLoad address: 0x43e00000
Oct 11 06:52:22.635173 \rLoading: *\b##
Oct 11 06:52:22.651084 \r 1.8 MiB/s
Oct 11 06:52:22.651119 \rdone
Oct 11 06:52:22.651144 \rBytes transferred = 26474 (676a hex)
Oct 11 06:52:22.651177 \rmissing environment variable: pxeuuid
Oct 11 06:52:22.659068 \rRetrieving file: pxelinux.cfg/AC10902D
Oct 11 06:52:22.659103 \rUsing asx0 device
Oct 11 06:52:22.659161 \rTFTP from server 172.16.144.3; our IP address is 172.16.144.45
Oct 11 06:52:22.667076 \rFilename 'pxelinux.cfg/AC10902D'.
Oct 11 06:52:22.675051 \rLoad address: 0x51000000
Oct 11 06:52:22.675082 \rLoading: *\b#
Oct 11 06:52:22.675106 \r 15.6 KiB/s
Oct 11 06:52:22.675131 \rdone
Oct 11 06:52:22.675153 \rBytes transferred = 65 (41 hex)
Oct 11 06:52:22.683067 \rConfig file found
Oct 11 06:52:22.683096 \rIgnoring unknown command: serial
Oct 11 06:52:22.683124 \r1: local
Oct 11 06:52:22.691033 \rscanning bus for devices...
Oct 11 06:52:22.691064 \r Device 0: (0:0) Vendor: ATA Prod.: HGST HTS545050A7 Rev: GG2O
Oct 11 06:52:22.715075 \r Type: Hard Disk
Oct 11 06:52:22.723062 \r Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Oct 11 06:52:22.723100 \rFound 1 device(s).
Oct 11 06:52:22.723126
Oct 11 06:52:22.723147 \rSCSI device 0:
Oct 11 06:52:22.731046 \r Device 0: (0:0) Vendor: ATA Prod.: HGST HTS545050A7 Rev: GG2O
Oct 11 06:52:22.731093 \r Type: Hard Disk
Oct 11 06:52:22.739063 \r Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Oct 11 06:52:22.739100 \r... is now current device
Oct 11 06:52:22.747037 \rScanning scsi 0...
Oct 11 06:52:22.747066 \rFound U-Boot script /boot.scr
Oct 11 06:52:22.907117 \r1710 bytes read in 34 ms (48.8 KiB/s)
Oct 11 06:52:22.947138 \r## Executing script at 50000000
Oct 11 06:52:22.955124 \rLoading dtbs/4.9.20+/exynos5250-arndale.dtb
Oct 11 06:52:22.955175 \r43128 bytes read in 1186 ms (35.2 KiB/s)
Oct 11 06:52:24.115168 \r917512 bytes read in 111 ms (7.9 MiB/s)
Oct 11 06:52:24.251222 \rLoaded xen-4.10-unstable to 0x41000000 (e0008)
Oct 11 06:52:24.259243 \rcommand line: conswitch=x watchdog noreboot console=dtuart dtuart=serial2 dom0_mem=512M,max:512M
Oct 11 06:52:24.267256 \r6798760 bytes read in 305 ms (21.3 MiB/s)
Oct 11 06:52:24.587101 \rLoaded vmlinuz-4.9.20+ to 0x42000000 (67bda8)
Oct 11 06:52:24.595066 \rcommand line: ro root=/dev/mapper/arndale--westfield--vg-root rootdelay=3 ro root=/dev/mapper/arndale--westfield--vg-root rootdelay=3 console=hvc0 clk_ignore_unused clk_ignore_unused
Oct 11 06:52:24.611018 \r12732874 bytes read in 655 ms (18.5 MiB/s)
Oct 11 06:52:25.251184 \rLoaded initrd.img-4.9.20+ to 0x43300000 (c249ca)
Oct 11 06:52:25.259100 \rchosen {
Oct 11 06:52:25.259133 \r #size-cells = <0x00000001>;
Oct 11 06:52:25.267097 \r #address-cells = <0x00000001>;
Oct 11 06:52:25.267130 \r bootargs = "conswitch=x watchdog noreboot console=dtuart dtuart=serial2 dom0_mem=512M,max:512M";
Oct 11 06:52:25.275189 \r module@1 {
Oct 11 06:52:25.275228 \r reg = <0x43300000 0x00c249ca>;
Oct 11 06:52:25.283076 \r compatible = "xen,linux-initrd", "xen,multiboot-module";
Oct 11 06:52:25.283116 \r };
Oct 11 06:52:25.283138 \r module@0 {
Oct 11 06:52:25.283162 \r bootargs = "ro root=/dev/mapper/arndale--westfield--vg-root rootdelay=3 ro root=/dev/mapper/arndale--westfield--vg-root rootdelay=3 console=hvc0 clk_ignore_unused clk_ignore_unused";
Oct 11 06:52:25.299122 \r reg = <0x42000000 0x0067bda8>;
Oct 11 06:52:25.307107 \r compatible = "xen,linux-zimage", "xen,multiboot-module";
Oct 11 06:52:25.307133 \r };
Oct 11 06:52:25.315083 \r};
Oct 11 06:52:25.315100 \rBooting 0x41000000 - 0x43000000
Oct 11 06:52:25.315116 \rKernel image @ 0x41000000 [ 0x000000 - 0x125780 ]
Oct 11 06:52:25.315133 \r## Flattened Device Tree blob at 43000000
Oct 11 06:52:25.323090 \r Booting using the fdt blob at 0x43000000
Oct 11 06:52:25.323110 \r reserving fdt memory region: addr=43000000 size=b000
Oct 11 06:52:25.331095 \r Loading Device Tree to 4fff2000, end 4fffffff ... OK
Oct 11 06:52:25.339059
Oct 11 06:52:25.339075 \rStarting kernel ...(fake run for tracing)
Oct 11 06:52:25.347045
Oct 11 06:52:25.347060
Oct 11 06:52:25.347072 \rStarting kernel ...
The trace from the Cubietruck looks the same.
Roger.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [xen-unstable-smoke test] 114332: regressions - FAIL
2017-10-11 7:30 ` Roger Pau Monné
@ 2017-10-11 14:30 ` Julien Grall
0 siblings, 0 replies; 3+ messages in thread
From: Julien Grall @ 2017-10-11 14:30 UTC (permalink / raw)
To: Roger Pau Monné, osstest service owner
Cc: Julien Grall, xen-devel, Stefano Stabellini
Hi,
On 11/10/17 08:30, Roger Pau Monné wrote:
> Adding Julien and Stefano.
>
> On Wed, Oct 11, 2017 at 07:17:59AM +0000, osstest service owner wrote:
>> flight 114332 xen-unstable-smoke real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/114332/
>>
>> Regressions :-(
>>
>> Tests which did not succeed and are blocking,
>> including tests which could not be run:
>> test-armhf-armhf-xl 7 xen-boot fail REGR. vs. 114299
>
> Seems like Xen is not able to start on the Exynos or Cubietrucks
> anymore:
I have posted a fix few minutes ago (see [1]). It is because on 32
environment, the assembler does seem to support 64-bit constant and will
ignore the top 32-bit.
Cheers,
[1]
https://lists.xenproject.org/archives/html/xen-devel/2017-10/msg01394.html
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2017-10-11 14:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-10-11 7:17 [xen-unstable-smoke test] 114332: regressions - FAIL osstest service owner
2017-10-11 7:30 ` Roger Pau Monné
2017-10-11 14:30 ` Julien Grall
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).