>>> On 13.06.15 at 01:15, wrote:
> On Jun 12, 2015 12:59 AM, "Jan Beulich" wrote:
>>
>> >>> On 12.06.15 at 01:23, wrote:
>> > There are two usages on MTRRs:
>> > 1) MTRR entries set by firmware
>> > 2) MTRR entries set by OS drivers
>> >
>> > We can obsolete 2), but we have no control over 1).
flight 58530 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58530/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-sedf 3 host-install(3) broken in 58451 pass in 58530
test-amd64-i386-xl-qemuu-winxps
On 06/12/2015 06:20 PM, Greg KH wrote:
On Fri, Jun 12, 2015 at 04:10:00PM +0200, Juergen Gross wrote:
Introduces the Xen pvUSB frontend. With pvUSB it is possible for a Xen
domU to communicate with a USB device assigned to that domU. The
communication is all done via the pvUSB backend in a drive
On 06/12/2015 06:23 PM, Greg KH wrote:
On Fri, Jun 12, 2015 at 04:09:59PM +0200, Juergen Gross wrote:
+enum usb_spec_version {
+ USB_VER_UNKNOWN = 0,
+ USB_VER_USB11,
+ USB_VER_USB20,
+ USB_VER_USB30, /* not supported yet */
+};
+
You are defining a bunch of things in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2015/5/25 8:56, Ben Hutchings wrote:
> This fix appears to be needed in all stable branches:
>
> commit a6dfa128ce5c414ab46b1d690f7a1b8decb8526d
> Author: Konrad Rzeszutek Wilk
> Date: Fri Apr 17 15:04:48 2015 -0400
>
> config: Enable NEED_
flight 58519 linux-3.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58519/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl 9 debian-install fail REGR. vs. 52209-bisect
test-amd64-amd64-pair
flight 58522 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58522/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 6 xen-boot fail REGR. vs. 58428
Regressions which are
On 2015/6/13 0:43, Wei Liu wrote:
On Thu, Jun 11, 2015 at 09:15:23AM +0800, Tiejun Chen wrote:
Here we'll construct a basic guest e820 table via
XENMEM_set_memory_map. This table includes lowmem, highmem
and RDMs if they exist. And hvmloader would need this info
later.
Signed-off-by: Tiejun Che
On 06/12/2015 10:35 PM, Wei Liu wrote:
On Mon, Jun 08, 2015 at 11:45:56AM +0800, Yang Hongyang wrote:
implement COLO nic subkind.
Signed-off-by: Yang Hongyang
Signed-off-by: Wen Congyang
---
tools/hotplug/Linux/Makefile | 1 +
tools/hotplug/Linux/colo-proxy-setup | 131
Hi Ian J, Wei,
On 06/12/2015 10:51 PM, Ian Jackson wrote:
Wei Liu writes ("Re: [Xen-devel] [PATCH v6 COLO 02/15] secondary vm
suspend/resume/checkpoint code"):
On Mon, Jun 08, 2015 at 11:45:46AM +0800, Yang Hongyang wrote:
From: Wen Congyang
+crcs->status = LIBXL_COLO_RESUMED;
+
+/*
On 06/12/2015 10:23 PM, Wei Liu wrote:
On Mon, Jun 08, 2015 at 11:45:46AM +0800, Yang Hongyang wrote:
From: Wen Congyang
Secondary vm is running in colo mode. So we will do
the following things again and again:
1. Resume secondary vm
a. Send LIBXL_COLO_SVM_READY to master.
b. If it i
On 2015/6/13 0:39, Wei Liu wrote:
On Thu, Jun 11, 2015 at 09:15:22AM +0800, Tiejun Chen wrote:
[...]
+++ b/tools/libxc/xc_hvm_build_x86.c
@@ -21,6 +21,7 @@
#include
#include
#include
+#include
#include "xg_private.h"
#include "xc_private.h"
@@ -270,7 +271,7 @@ static int setup_gue
On 06/11/2015 06:55 PM, Ian Campbell wrote:
On Thu, 2015-06-11 at 11:45 +0100, Andrew Cooper wrote:
On 11/06/15 09:41, Ian Campbell wrote:
On Thu, 2015-06-11 at 10:07 +0800, Yang Hongyang wrote:
On 06/10/2015 11:20 PM, Ian Campbell wrote:
On Mon, 2015-06-08 at 11:43 +0800, Yang Hongyang wro
On 06/12/2015 09:28 PM, Wei Liu wrote:
On Mon, Jun 08, 2015 at 11:43:17AM +0800, Yang Hongyang wrote:
Checkpoint device is an abstract layer to do checkpoint.
COLO can also use it to do checkpoint. But there are
still some codes in checkpoint device which touch remus:
1. remus_ops: we use remu
On 06/12/2015 10:57 PM, Ian Jackson wrote:
Wei Liu writes ("Re: [Xen-devel] [PATCH v2 COLOPre 11/13] tools/libxl: rename remus
device to checkpoint device"):
On Fri, Jun 12, 2015 at 02:30:46PM +0100, Wei Liu wrote:
On Mon, Jun 08, 2015 at 11:43:15AM +0800, Yang Hongyang wrote:
-(-18, "R
On 06/12/2015 11:04 PM, Ian Jackson wrote:
Wei Liu writes ("Re: [Xen-devel] [PATCH v2 COLOPre 10/13] tools/libxl: Add back
channel to allow migration target send data back"):
On Mon, Jun 08, 2015 at 11:43:14AM +0800, Yang Hongyang wrote:
From: Wen Congyang
In colo mode, slave needs to send
On 06/12/2015 08:54 PM, Wei Liu wrote:
On Mon, Jun 08, 2015 at 11:43:14AM +0800, Yang Hongyang wrote:
From: Wen Congyang
In colo mode, slave needs to send data to master, but the io_fd
only can be written in master, and only can be read in slave.
Save recv_fd in domain_suspend_state, and sen
On 06/12/2015 08:33 PM, Wei Liu wrote:
On Mon, Jun 08, 2015 at 11:43:11AM +0800, Yang Hongyang wrote:
Currently, libxl__domain_unpause() only supports
qemu-xen-traditional. Update it to support qemu-xen.
Signed-off-by: Wen Congyang
Signed-off-by: Yang Hongyang
This looks very similar to a
On 2015/6/13 0:17, Wei Liu wrote:
On Thu, Jun 11, 2015 at 09:15:21AM +0800, Tiejun Chen wrote:
This patch passes our rdm reservation policy inside libxl
when we assign a device or attach a device.
Signed-off-by: Tiejun Chen
---
docs/man/xl.pod.1 | 7 ++-
tools/libxl/libxl_pci.c
On 2015/6/13 0:02, Wei Liu wrote:
On Thu, Jun 11, 2015 at 09:15:20AM +0800, Tiejun Chen wrote:
This patch introduces user configurable parameters to specify RDM
resource and according policies,
Global RDM parameter:
rdm = "type=none/host,reserve=strict/relaxed"
Per-device RDM parameter:
Hi Parth,
On 14/06/2015 11:27, Parth Dixit wrote:
On 8 June 2015 at 22:20, Julien Grall wrote:
Hi Parth,
On 17/05/2015 21:03, Parth Dixit wrote:
In ACPI mmio regions are described in DSDT which requires
AML interpreter. Defer the mapping of mmio until DSDT is parsed in
DOM0 and map mmio's d
On 2015/6/12 23:43, Wei Liu wrote:
On Thu, Jun 11, 2015 at 09:15:19AM +0800, Tiejun Chen wrote:
[...]
-static int next_bdf(char **str, int *seg, int *bus, int *dev, int *func)
+static int next_bdf(char **str, int *seg, int *bus, int *dev, int *func,
+int *flag)
This is unr
On 12/06/2015 19:40, Julien Grall wrote:
> On 11/06/2015 22:01, Wang, Wei W wrote:
> > On 11/06/2015 22:06, Julien Grall wrote:
> >> On 11/06/2015 04:28, Wei Wang wrote:
> >>> cpufreq_cpu_policy is used in intel_pstate_set_pstate(), so we
> >>> change to NULL it after the call of cpufreq_driver->ex
On 12/06/2015 19:30, Julien Grall wrote:
> On 11/06/2015 21:41, Wang, Wei W wrote:
> > On 11/06/2015 22:02, Julien Grall wrote:
> >> On 11/06/2015 04:27, Wei Wang wrote:
> >>> diff --git a/xen/include/acpi/cpufreq/cpufreq.h
> >> b/xen/include/acpi/cpufreq/cpufreq.h
> >>> index d10e4c7..71bb45c 1006
On 12/06/2015 19:14, Julien Grall wrote:
> On 11/06/2015 23:03, Wang, Wei W wrote:
> > On 11/06/2015 22:02, Julien Grall wrote:
> >> On 11/06/2015 04:31, Wei Wang wrote:
> >>> -list_for_each(pos, &cpufreq_governor_list)
> >>> +if (policy->policy)
> >>
> >> What if another cpufreq decides to
flight 58510 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58510/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-libvirt 11 guest-start fail like 58426
test-amd64-amd64-libvirt 11 gu
flight 58528 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58528/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail like 58276
test-amd64-i386-xl-qemut-w
flight 58502 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58502/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 3 host-install(3) broken REGR. vs. 58392
test-amd64-amd64-xl-
branch xen-unstable
xen branch xen-unstable
job test-amd64-amd64-xl-xsm
test xen-boot
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/staging/qemu-xen-unstable.git
Tree: qemuu git://xenbits.xen.
flight 58473 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58473/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-amd64 14 guest-localmigrate.2 fail REGR.
vs. 58318
Regression
On 8 June 2015 at 22:20, Julien Grall wrote:
> Hi Parth,
>
> On 17/05/2015 21:03, Parth Dixit wrote:
>>
>> In ACPI mmio regions are described in DSDT which requires
>> AML interpreter. Defer the mapping of mmio until DSDT is parsed in
>> DOM0 and map mmio's dynamically at the time of request.
>
>
flight 58460 xen-4.2-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58460/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail REGR. vs.
58411
test-amd64-
On Fri, 2015-06-12 at 16:28 +0100, Ian Jackson wrote:
> Ian Jackson writes ("RE: [OSSTEST Nested PATCH v11 6/7] Compose the main
> recipe of nested test job"):
> > Thinking about this leads me to ask another question. Suppose that a
> > bug causes the l1 to lock up completely. ts-logs-capture wi
On Fri, 2015-06-12 at 16:27 +0100, Ian Jackson wrote:
> Pang, LongtaoX writes ("RE: [OSSTEST Nested PATCH v11 6/7] Compose the main
> recipe of nested test job"):
> > > From: Ian Jackson [mailto:ian.jack...@eu.citrix.com]
> ...
> > > leak-check compares the set of objects present at the `leak-chec
flight 58451 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58451/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 14 guest-localmigrate.2 fail REGR.
vs. 57474
Regressio
flight 58450 xen-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58450/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-rumpuserxen-amd64 15
rumpuserxen-demo-xenstorels/xenstorels.repeat fail REGR. v
flight 58525 rumpuserxen real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58525/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 5 rumpuserxen-build fail REGR. vs. 33866
build-i386-rumpuserxe
37 matches
Mail list logo
