[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable-smoke test] 84118: trouble: broken/pass
flight 84118 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/84118/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-debianhvm-i386 3 host-install(3) broken REGR. vs. 83972 Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-xl 12 migrate-support-check fail never pass test-armhf-armhf-xl 13 saverestore-support-check fail never pass version targeted for testing: xen 2753e07f5e8440cd5751369f5a037a7824e5a29e baseline version: xen abf8824fe530bcf060c757596f68663c87546a6a Last test of basis 83972 2016-02-25 13:01:35 Z 1 days Testing same since 84118 2016-02-26 12:03:38 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Bob Moore <robert.moore@xxxxxxxxx> David Vrabel <david.vrabel@xxxxxxxxxx> Doug Goldstein <cardoe@xxxxxxxxxx> Hanjun Guo <hanjun.guo@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Kevin Tian <kevin.tian@xxxxxxxxx> Liang Z Li <liang.z.li@xxxxxxxxx> Parth Dixit <parth.dixit@xxxxxxxxxx> Shannon Zhao <shannon.zhao@xxxxxxxxxx> Tim Deegan <tim@xxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> jobs: build-amd64 pass build-armhf pass build-amd64-libvirt pass test-armhf-armhf-xl pass test-amd64-amd64-xl-qemuu-debianhvm-i386 broken 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 broken-step test-amd64-amd64-xl-qemuu-debianhvm-i386 host-install(3) Not pushing. ------------------------------------------------------------ commit 2753e07f5e8440cd5751369f5a037a7824e5a29e Author: Shannon Zhao <shannon.zhao@xxxxxxxxxx> Date: Fri Feb 26 12:37:50 2016 +0100 arm/acpi: Initialize serial port from ACPI SPCR table Parse ACPI SPCR (Serial Port Console Redirection table) table and initialize the serial port pl011. Signed-off-by: Parth Dixit <parth.dixit@xxxxxxxxxx> Signed-off-by: Shannon Zhao <shannon.zhao@xxxxxxxxxx> Reviewed-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Fix build. Acked-by: Jan Beulich <jbeulich@xxxxxxxx> commit d5e8732bcad85b4166fba6e54724740a9e973691 Author: Bob Moore <robert.moore@xxxxxxxxx> Date: Fri Feb 26 12:37:18 2016 +0100 ACPICA / Headers: Add support for CSRT and DBG2 ACPI tables These tables are defined outside of the ACPI specification. Signed-off-by: Bob Moore <robert.moore@xxxxxxxxx> [Linux commit 4e2f9c278ad84196991fcf6f6646a3e15967fe90] [only port the DBG2 changes] Signed-off-by: Shannon Zhao <shannon.zhao@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> commit 89b5aa9bf74ebd4fcec06be05024e127361903a6 Author: Hanjun Guo <hanjun.guo@xxxxxxxxxx> Date: Fri Feb 26 12:36:46 2016 +0100 ACPI / table: Print GIC information when MADT is parsed When MADT is parsed, print GIC information as debug message: ACPI: GICC (acpi_id[0x0000] address[00000000e112f000] MPIDR[0x0] enabled) ACPI: GICC (acpi_id[0x0001] address[00000000e112f000] MPIDR[0x1] enabled) ... ACPI: GICC (acpi_id[0x0201] address[00000000e112f000] MPIDR[0x201] enabled) This debug information will be very helpful to bring up early systems to see if acpi_id and MPIDR are matched or not as spec defined. Signed-off-by: Hanjun Guo <hanjun.guo@xxxxxxxxxx> [Linux commit 4c1c8d7a7ebc8b909493a14b21b233e5377b69aa] [Use container_of instead of cast and PRIx64 instead of %llx] Signed-off-by: Shannon Zhao <shannon.zhao@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> commit 763076cf5d29b41c98171ac2489e1726f95667ae Author: Doug Goldstein <cardoe@xxxxxxxxxx> Date: Fri Feb 26 12:35:46 2016 +0100 build: convert HAS_CORE_PARKING to Kconfig Convert HAS_CORE_PARKING to Kconfig as CONFIG_CORE_PARKING. While removing HAS_CORE_PARKING, removed a trailing whitespace on a near by line. Signed-off-by: Doug Goldstein <cardoe@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 1afea8d3a9b947912e6be587b462a159fc7cd5d2 Author: Doug Goldstein <cardoe@xxxxxxxxxx> Date: Fri Feb 26 12:33:14 2016 +0100 build: convert HAS_NUMA to Kconfig Convert HAS_NUMA to Kconfig as CONFIG_NUMA and let CONFIG_NUMA be defined by Kconfig. Signed-off-by: Doug Goldstein <cardoe@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit fb1e853c53580c4d9be3519e552141805b75b19c Author: Doug Goldstein <cardoe@xxxxxxxxxx> Date: Fri Feb 26 12:31:47 2016 +0100 build: consolidate CONFIG_HAS_ACPI and CONFIG_ACPI No real advantage to keeping these separate. The use case of this from Linux is when the platform or target board has support for something but the user wants to be given the option to disable it. Signed-off-by: Doug Goldstein <cardoe@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 3d26674d088ab0d0f197bbfafaba3767d195986b Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri Feb 26 12:31:11 2016 +0100 printk: introduce separator modifiers for the %ph custom format The printk formats %*ph{C,D,N} are chosen to be compatible with their Linux counterparts. Sample: (XEN) buf: 00 01 03 07 78 65 6e 00 (XEN) buf: 00:01:03:07:78:65:6e:00 (XEN) buf: 00-01-03-07-78-65-6e-00 (XEN) buf: 0001030778656e00 Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit df5ded9a768893ebf0e479d6e4f51d5d4f31a05e Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri Feb 26 12:30:55 2016 +0100 docs: update README to include Clang Xen now builds on x86 with Clang 3.5 and 3.8. Update README to reflect this. Mark Clang as no longer a permitted failure in Travis, to prevent future regressions slipping back in. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Doug Goldstein <cardoe@xxxxxxxxxx> commit 5d768fb1f3f7b011e7b6e75909c7f4841730de60 Author: David Vrabel <david.vrabel@xxxxxxxxxx> Date: Fri Feb 26 12:30:11 2016 +0100 x86/hvm: add HVM_PARAM_X87_FIP_WIDTH The HVM parameter HVM_PARAM_X87_FIP_WIDTH to allow tools and the guest to adjust the width of the FIP/FDP registers to be saved/restored by the hypervisor. This is in case the hypervisor hueristics do not do the right thing. Add this parameter to the set saved during domain save/migrate. Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> commit 879b44b041f26de35e4b527bf0f3c361eb52bd82 Author: David Vrabel <david.vrabel@xxxxxxxxxx> Date: Fri Feb 26 12:16:13 2016 +0100 x86/fpu: add a per-domain field to set the width of FIP/FDP The x86 architecture allows either: a) the 64-bit FIP/FDP registers to be restored (clearing FCS and FDS); or b) the 32-bit FIP/FDP and FCS/FDS registers to be restored (clearing the upper 32-bits). Add a per-domain field to indicate which of these options a guest needs. The options are: 8, 4 or 0. Where 0 indicates that the hypervisor should automatically guess the FIP width by checking the value of FIP/FDP when saving the state (this is the existing behaviour). The FIP width is initially automatic but is set explicitly in the following cases: - 32-bit PV guest: 4 - Newer CPUs that do not save FCS/FDS: 8 The x87_fip_width field is placed into an existing 1 byte hole in struct arch_domain. Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx> Fix build. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> commit 825c6dddf5993ab6b84590026cd7b5454a7d5e94 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri Feb 26 12:15:36 2016 +0100 vVMX: use latched VMCS machine address Instead of calling domain_page_map_to_mfn() over and over, latch the guest VMCS machine address unconditionally (i.e. independent of whether VMCS shadowing is supported by the hardware). Since this requires altering the parameters of __[gs]et_vmcs{,_real}() (and hence all their callers) anyway, take the opportunity to also drop the bogus double underscores from their names (and from __[gs]et_vmcs_virtual() as well). Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Tested-by: Liang Z Li <liang.z.li@xxxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> commit 158ba53323cc0fcdb833798139a2f20a15dad5e2 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri Feb 26 12:15:09 2016 +0100 x86emul: simplify IRET logic Since we only handle real mode, we need to consider neither non-ring0 nor IOPL. Also for POPF the mode_iopl() check can really be inside the not-ring-0 body. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 81d3a0b26c1672c60b2a54dd8780e6f6472d2328 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri Feb 26 12:14:39 2016 +0100 x86emul: limit-check branch targets All branches need to #GP when their target violates the segment limit (in 16- and 32-bit modes) or is non-canonical (in 64-bit mode). For near branches facilitate this via a zero-byte instruction fetch from the target address (resulting in address translation and validation without an actual read from memory), while far branches get dealt with by breaking up the segment register loading into a read-and-validate part and a write one. The latter at once allows correcting some ordering issues in how the individual emulation steps get carried out: Before updating machine state, all exceptions unrelated to that state updating should have got raised (i.e. the only ones possibly resulting in partly updated state are faulting memory writes [pushes]). Note that while not immediately needed here, write and distinct read emulation routines get updated to deal with zero byte accesses too, for overall consistency. Reported-by: å??令 <liuling-it@xxxxxx> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> (qemu changes not included) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |