|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [xen-unstable test] 9955: regressions - FAIL
On 22/11/2011 07:17, "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx> wrote: > flight 9955 xen-unstable real [real] > http://www.chiark.greenend.org.uk/~xensrcts/logs/9955/ > > Regressions :-( > > Tests which did not succeed and are blocking: > test-amd64-amd64-xl-sedf 11 guest-localmigrate fail in 9951 REGR. vs. > 9855 Could c/s 24160 be to blame? -- Keir > Tests which are failing intermittently (not blocking): > test-i386-i386-win 14 guest-start.2 fail pass in > 9951 > > Tests which did not succeed, but are not blocking, > including regressions (tests previously passed) regarded as allowable: > test-amd64-amd64-xl-sedf 5 xen-boot fail like > 9817 > test-amd64-i386-rhel6hvm-intel 9 guest-start.2 fail never > pass > test-amd64-i386-rhel6hvm-amd 9 guest-start.2 fail never > pass > test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never > pass > test-amd64-amd64-xl-win 13 guest-stop fail never > pass > test-amd64-i386-win-vcpus1 16 leak-check/check fail never > pass > test-amd64-i386-win 16 leak-check/check fail never > pass > test-amd64-i386-xl-win-vcpus1 13 guest-stop fail never > pass > test-i386-i386-xl-win 13 guest-stop fail never > pass > test-amd64-amd64-win 16 leak-check/check fail never > pass > test-i386-i386-win 16 leak-check/check fail in 9951 never > pass > > version targeted for testing: > xen 0a0c02a61676 > baseline version: > xen dbdc840f8f62 > > ------------------------------------------------------------ > People who touched revisions under test: > Andrew Cooper <andrew.cooper3@xxxxxxxxxx> > Charles Arnold <carnold@xxxxxxxx> > Ian Campbell <ian.campbell@xxxxxxxxxx> > Jan Beulich <jbeulich@xxxxxxxx> > Jean Guyader <jean.guyader@xxxxxxxxxxxxx> > Juergen Gross <juergen.gross@xxxxxxxxxxxxxx> > Keir Fraser <keir@xxxxxxx> > Olaf Hering <olaf@xxxxxxxxx> > Paul Durrant <paul.durrant@xxxxxxxxxx> > ------------------------------------------------------------ > > jobs: > build-amd64 pass > build-i386 pass > build-amd64-oldkern pass > build-i386-oldkern pass > build-amd64-pvops pass > build-i386-pvops pass > test-amd64-amd64-xl pass > test-amd64-i386-xl pass > test-i386-i386-xl pass > test-amd64-i386-rhel6hvm-amd fail > test-amd64-i386-xl-credit2 pass > test-amd64-amd64-xl-pcipt-intel fail > test-amd64-i386-rhel6hvm-intel fail > test-amd64-i386-xl-multivcpu pass > test-amd64-amd64-pair pass > test-amd64-i386-pair pass > test-i386-i386-pair pass > test-amd64-amd64-pv pass > test-amd64-i386-pv pass > test-i386-i386-pv pass > test-amd64-amd64-xl-sedf fail > test-amd64-i386-win-vcpus1 fail > test-amd64-i386-xl-win-vcpus1 fail > test-amd64-amd64-win fail > test-amd64-i386-win fail > test-i386-i386-win fail > test-amd64-amd64-xl-win fail > test-i386-i386-xl-win fail > > > ------------------------------------------------------------ > sg-report-flight on woking.cam.xci-test.com > logs: /home/xc_osstest/logs > images: /home/xc_osstest/images > > Logs, config files, etc. are available at > http://www.chiark.greenend.org.uk/~xensrcts/logs > > Test harness code can be found at > http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary > > > Not pushing. > > ------------------------------------------------------------ > changeset: 24169:0a0c02a61676 > tag: tip > user: Keir Fraser <keir@xxxxxxx> > date: Mon Nov 21 21:28:34 2011 +0000 > > hvmloader: Fix memory relocation loop. > > Signed-off-by: Keir Fraser <keir@xxxxxxx> > > > changeset: 24168:9c350ab8d3ea > user: Jan Beulich <jbeulich@xxxxxxxx> > date: Mon Nov 21 09:29:31 2011 +0100 > > x86/vioapic: clear remote IRR when switching RTE to edge triggered mode > > Xen itself (as much as Linux) relies on this behavior, so it should > also emulate it properly. Not doing so reportedly gets in the way of > kexec inside a HVM guest. > > Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> > Tested-by: Olaf Hering <olaf@xxxxxxxxx> > > > changeset: 24167:335e8273a3f3 > user: Keir Fraser <keir@xxxxxxx> > date: Sat Nov 19 22:13:51 2011 +0000 > > x86: Fix RCU locking in XENMEM_add_to_physmap. > > Signed-off-by: Keir Fraser <keir@xxxxxxx> > > > changeset: 24166:fe3e9d0c123c > user: Jean Guyader <jean.guyader@xxxxxxxxxxxxx> > date: Fri Nov 18 13:43:26 2011 +0000 > > iommu: Introduce per cpu flag (iommu_dont_flush_iotlb) to avoid > unnecessary iotlb flush > > Add cpu flag that will be checked by the iommu low level code > to skip iotlb flushes. iommu_iotlb_flush shall be called explicitly. > > Signed-off-by: Jean Guyader <jean.guyader@xxxxxxxxxxxxx> > Committed-by: Keir Fraser <keir@xxxxxxx> > > > changeset: 24165:89a4d97731c5 > user: Jean Guyader <jean.guyader@xxxxxxxxxxxxx> > date: Fri Nov 18 13:42:46 2011 +0000 > > hvmloader: Change memory relocation loop when overlap with PCI hole > > Change the way we relocate the memory page if they overlap with pci > hole. Use new map space (XENMAPSPACE_gmfn_range) to move the loop > into xen. > > This code usually get triggered when a device is pass through to a > guest and the PCI hole has to be extended to have enough room to map > the device BARs. The PCI hole will starts lower and it might overlap > with some RAM that has been alocated for the guest. That usually > happen if the guest has more than 4G of RAM. We have to relocate > those pages in high mem otherwise they won't be accessible. > > Signed-off-by: Jean Guyader <jean.guyader@xxxxxxxxxxxxx> > Committed-by: Keir Fraser <keir@xxxxxxx> > > > changeset: 24164:707d27fe03e7 > user: Jean Guyader <jean.guyader@xxxxxxxxxxxxx> > date: Fri Nov 18 13:42:08 2011 +0000 > > mm: New XENMEM space, XENMAPSPACE_gmfn_range > > XENMAPSPACE_gmfn_range is like XENMAPSPACE_gmfn but it runs on > a range of pages. The size of the range is defined in a new field. > > This new field .size is located in the 16 bits padding between .domid > and .space in struct xen_add_to_physmap to stay compatible with older > versions. > > Signed-off-by: Jean Guyader <jean.guyader@xxxxxxxxxxxxx> > Committed-by: Keir Fraser <keir@xxxxxxx> > > > changeset: 24163:7a9a1261a6b0 > user: Jean Guyader <jean.guyader@xxxxxxxxxxxxx> > date: Fri Nov 18 13:41:33 2011 +0000 > > add_to_physmap: Move the code for XENMEM_add_to_physmap > > Move the code for the XENMEM_add_to_physmap case into it's own > function (xenmem_add_to_physmap). > > Signed-off-by: Jean Guyader <jean.guyader@xxxxxxxxxxxxx> > Committed-by: Keir Fraser <keir@xxxxxxx> > > > changeset: 24162:9a1a71f7bef2 > user: Jean Guyader <jean.guyader@xxxxxxxxxxxxx> > date: Fri Nov 18 13:40:56 2011 +0000 > > iommu: Introduce iommu_flush and iommu_flush_all. > > Signed-off-by: Jean Guyader <jean.guyader@xxxxxxxxxxxxx> > Committed-by: Keir Fraser <keir@xxxxxxx> > > > changeset: 24161:aeb628c5af3f > user: Jean Guyader <jean.guyader@xxxxxxxxxxxxx> > date: Fri Nov 18 13:40:19 2011 +0000 > > vtd: Refactor iotlb flush code > > Factorize the iotlb flush code from map_page and unmap_page into > it's own function. > > Signed-off-by: Jean Guyader <jean.guyader@xxxxxxxxxxxxx> > Committed-by: Keir Fraser <keir@xxxxxxx> > > > changeset: 24160:d7e6bfa114d0 > user: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx> > date: Fri Nov 18 13:34:43 2011 +0000 > > sched_sedf: Avoid panic when adjusting sedf parameters > > When using sedf scheduler in a cpupool the system might panic when > setting sedf scheduling parameters for a domain. Introduces > for_each_domain_in_cpupool macro as it is usable 4 times now. Add > appropriate locking in cpupool_unassign_cpu(). > > Signed-off-by: Juergen Gross <juergen.gross@xxxxxxxxxxxxxx> > Committed-by: Keir Fraser <keir@xxxxxxx> > > > changeset: 24159:0965e589fdcc > user: Paul Durrant <paul.durrant@xxxxxxxxxx> > date: Fri Nov 18 13:32:50 2011 +0000 > > hvmloader: Add configuration options to selectively disable S3 and S4 ACPI > power states. > > Introduce acpi_s3 and acpi_s4 configuration options (default=1). The > S3 and S4 packages are moved into separate SSDTs and their inclusion > is controlled by the new configuration options. > > Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx> > Committed-by: Keir Fraser <keir@xxxxxxx> > > > changeset: 24158:4fa1c13f8bb1 > user: Paul Durrant <paul.durrant@xxxxxxxxxx> > date: Fri Nov 18 13:31:43 2011 +0000 > > hvmloader: Move acpi_enabled out of hvm_info_table into xenstore > > Since hvmloader has a xentore client, use a platform key in xenstore > to indicate whether ACPI is enabled or not rather than the shared > hvm_info_table structure. > > Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx> > Committed-by: Keir Fraser <keir@xxxxxxx> > > > changeset: 24157:7b5e1cb94bfa > user: Jan Beulich <jbeulich@xxxxxxxx> > date: Fri Nov 18 09:22:45 2011 +0100 > > x86/xsave: provide guests with finit-like environment > > Without the use of xsave, guests get their initial floating point > environment set up with finit. At least NetWare actually depends on > this (in particular on all exceptions being masked), so to be > consistent set the same environment also when using xsave. This is > also in line with all SSE exceptions getting masked initially. > > To avoid further fragile casts in xstate_alloc_save_area() the patch > also changes xsave_struct's fpu_see member to have actually usable > fields. > > The patch was tested in its technically identical, but modified-file- > wise different 4.1.2 version. > > Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> > Tested-by: Charles Arnold <carnold@xxxxxxxx> > Acked-by: Keir Fraser <keir@xxxxxxx> > > > changeset: 24156:f29b5bd6e25f > user: Jan Beulich <jbeulich@xxxxxxxx> > date: Fri Nov 18 09:21:24 2011 +0100 > > x86/IRQ: prevent vector sharing within IO-APICs > > Following the prevention of vector sharing for MSIs, this change > enforces the same within IO-APICs: Pin based interrupts use the IO-APIC > as their identifying device under the AMD IOMMU (and just like for > MSIs, only the identifying device is used to remap interrupts here, > with no regard to an interrupt's destination). > > Additionally, LAPIC initiated EOIs (for level triggered interrupts) too > use only the vector for identifying which interrupts to end. While this > generally causes no significant problem (at worst an interrupt would be > re-raised without a new interrupt event actually having occurred), it > still seems better to avoid the situation. > > For this second aspect, a distinction is being made between the > traditional and the directed-EOI cases: In the former, vectors should > not be shared throughout all IO-APICs in the system, while in the > latter case only individual IO-APICs need to be contrained (or, if the > firmware indicates so, sub- groups of them having the same GSI appear > at multiple pins). > > Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> > Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> > > > changeset: 24155:0d50e704834f > user: Jan Beulich <jbeulich@xxxxxxxx> > date: Fri Nov 18 09:18:41 2011 +0100 > > x86/IO-APIC: refine EOI-ing of migrating level interrupts > > Rather than going through all IO-APICs and calling io_apic_eoi_vector() > for the vector in question, just use eoi_IO_APIC_irq(). > > This in turn allows to eliminate quite a bit of other code. > > Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> > Tested-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> > Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> > > > changeset: 24154:dbdc840f8f62 > user: Keir Fraser <keir@xxxxxxx> > date: Wed Nov 16 18:21:14 2011 +0000 > > elf: Fix Elf64 types and structs to match the specification. > > The layouts were actually correct, but the type names were a bit > messed up. > > Original patch by Volker Eckert <volker.eckert@xxxxxxxxxx> > Signed-off-by: Keir Fraser <keir@xxxxxxx> > > > ======================================== > commit 52834188eedfbbca5636fd869d4c86b3b3044439 > Author: Ian Campbell <ian.campbell@xxxxxxxxxx> > Date: Tue Nov 1 18:42:55 2011 +0000 > > qemu-xen: remove i386-dm/README.hvm-pv-magic-ioport-disable > > I have just proposed a patch to add this to xen-unstable.hg as > docs/misc/hvm-emulated-unplug.markdown. This repo is not a place where > people > look for docs, plus we are transitioning to upstream qemu. > > Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> > > _______________________________________________ > Xen-devel mailing list > Xen-devel@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |