From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [qemu-upstream-unstable test] 18197: regressions - trouble: blocked/broken/fail/pass
Date: Tue, 25 Jun 2013 17:20:13 +0100 [thread overview]
Message-ID: <osstest-18197-mainreport@xen.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 7711 bytes --]
flight 18197 qemu-upstream-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/18197/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386 3 host-build-prep fail REGR. vs. 18112
Tests which did not succeed, but are not blocking:
test-amd64-i386-qemuu-rhel6hvm-amd 1 xen-build-check(1) blocked n/a
test-amd64-i386-qemuu-rhel6hvm-intel 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass
test-amd64-i386-xend-qemuu-winxpsp3 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 1 xen-build-check(1) blocked n/a
test-amd64-i386-xl-qemuu-win7-amd64 1 xen-build-check(1) blocked n/a
test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass
version targeted for testing:
qemuu 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
baseline version:
qemuu 79c097d5fe7cb0b4788ed509240cde7e210650bf
------------------------------------------------------------
People who touched revisions under test:
Andreas Färber <afaerber@suse.de>
Anthony PERARD <anthony.perard@citrix.com>
Igor Mammedov <imammedo@redhat.com>
Luiz Capitulino <lcapitulino@redhat.com>
Michael S. Tsirkin <mst@redhat.com>
------------------------------------------------------------
jobs:
build-amd64 pass
build-armhf pass
build-i386 broken
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-i386-qemuu-rhel6hvm-amd blocked
test-amd64-amd64-xl-qemuu-win7-amd64 fail
test-amd64-i386-xl-qemuu-win7-amd64 blocked
test-amd64-i386-qemuu-rhel6hvm-intel blocked
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 blocked
test-amd64-i386-xend-qemuu-winxpsp3 blocked
test-amd64-amd64-xl-qemuu-winxpsp3 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.
------------------------------------------------------------
commit 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
Merge: 79c097d... 35bdc13...
Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Date: Tue Jun 25 11:34:24 2013 +0000
Merge remote branch 'perard/cpu-hotplug-port-v2' into xen-staging-master-7
commit 35bdc13b52197d7e9dcadd5af9621b6463290300
Author: Anthony PERARD <anthony.perard@citrix.com>
Date: Mon Jun 10 15:29:31 2013 +0100
xen: Implement hot_add_cpu hook.
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
commit f573cdfa7afa92ebb66b2ba066b4f08bd22fc84b
Author: Anthony PERARD <anthony.perard@citrix.com>
Date: Fri Jun 14 14:43:05 2013 +0100
xen: Fix vcpus initialisation.
Each vcpu needs a call to xc_evtchn_bind_interdomain in QEMU, even those
that are unplug at QEMU initialisation.
Without this patch, any hot-plugged CPU will be "Stuck ??" when Linux
will try to use them.
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
commit 647e2f8c9c34947130c50e593a51fa50e9904145
Author: Igor Mammedov <imammedo@redhat.com>
Date: Tue Apr 30 15:41:25 2013 +0200
QMP: Add cpu-add command
Adds "cpu-add id=xxx" QMP command.
cpu-add's "id" argument is a CPU number in a range [0..max-cpus)
Example QMP command:
-> { "execute": "cpu-add", "arguments": { "id": 2 } }
<- { "return": {} }
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Acked-by: Luiz Capitulino <lcapitulino@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
(cherry picked from QEMU commit 69ca3ea5e192251f27510554611bcff6f036a00b)
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
commit 4b8e1c9837aef6297a2899fb2115c0b179250732
Author: Igor Mammedov <imammedo@redhat.com>
Date: Tue Apr 30 15:41:24 2013 +0200
Add hot_add_cpu hook to QEMUMachine
Hook should be set by machines that implement CPU hot-add
via cpu-add QMP command.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
(cherry picked from QEMU commit b4fc7b4326112538e0dbdc7fd019652ba8cc3281)
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
commit 385226be3a600c871a2cf306fca0e2788791293b
Author: Igor Mammedov <imammedo@redhat.com>
Date: Thu Apr 25 16:05:25 2013 +0200
acpi_piix4: Add infrastructure to send CPU hot-plug GPE to guest
* introduce processor status bitmask visible to guest at 0xaf00 addr,
where ACPI asl code expects it
* set bit corresponding to APIC ID in processor status bitmask on
receiving CPU hot-plug notification
* trigger CPU hot-plug SCI, to notify guest about CPU hot-plug event
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
(cherry picked from QEMU commit b8622725cf0196f672f272922b0941dc8ba1c408)
The function piix4_cpu_hotplug_req() has been modified to take an integer
instead of a CPU object.
There was a cpu_added_notifier in the original commit, this haven't
been back-ported, as it can't be used.
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
commit 0170b3ce88cb87346afa369a89ce9b197389058b
Author: Michael S. Tsirkin <mst@redhat.com>
Date: Wed Apr 24 22:58:04 2013 +0200
cpu: Add qemu_for_each_cpu()
Wrapper to avoid open-coded loops and to make CPUState iteration
independent of CPUArchState.
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
(cherry picked from QEMU commit d6b9e0d60cc511eca210834428bb74508cff3d33)
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
commit e48f3af500a229bf9bf63fbe02ca6ef35abc2820
Author: Igor Mammedov <imammedo@redhat.com>
Date: Tue Apr 23 10:29:41 2013 +0200
cpu: Introduce get_arch_id() method and override it for X86CPU
get_arch_id() adds possibility for generic code to get a guest-visible
CPU ID without accessing CPUArchState.
If derived classes don't override it, it will return cpu_index.
Override it on target-i386 in X86CPU to return the APIC ID.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
Reviewed-by: liguang <lig.fnst@cn.fujitsu.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Andreas Färber <afaerber@suse.de>
(cherry picked from QEMU commit 997395d3888fcde6ce41535a8208d7aa919d824b)
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
reply other threads:[~2013-06-25 16:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=osstest-18197-mainreport@xen.org \
--to=ian.jackson@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).