flight 58976 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58976/
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. vs. 58
flight 58983 rumpuserxen real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58983/
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
Signed-off-by: Wen Congyang
---
tools/libxl/libxl_netbuffer.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/libxl/libxl_netbuffer.c b/tools/libxl/libxl_netbuffer.c
index ff2d6c7..107e867 100644
--- a/tools/libxl/libxl_netbuffer.c
+++ b/tools/libxl/libxl_netbuffer.c
On 06/26/2015 01:44 AM, Ian Jackson wrote:
> Change the timeout setup functions to take a libxl__ao, not a
> libxl__gc. This is going to be needed for ao abort, because timeouts
> are going to be a main hook for ao abort requests - so the timeouts
> need to be associated with an ao.
>
> This mean
flight 58975 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58975/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-sedf-pin 3 host-install(3) broken pass in 58969
test-armhf-armhf-xl-multivcpu 1
flight 58974 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58974/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs. 58965
Reg
>
> == Hypervisor ==
>
> * Improve RTDS scheduler (ok)
>Change RTDS from quantum driven to event driven
> - Dagaen Golomb, Meng Xu, Chong Li
As to changing the RTDS scheduler from quantum driven to event driven
(in Hypervisor):
Dagaen sent the second version of patch that reflects Dario's
Hi Ian and Dario,
Thank you very much for your explanation!
2015-06-29 2:33 GMT-07:00 Dario Faggioli :
>
> On Mon, 2015-06-29 at 09:53 +0100, Ian Campbell wrote:
> > On Sat, 2015-06-27 at 12:05 -0700, Meng Xu wrote:
>
> > > I want/hope to know when/how the RTDS scheduler fails the test so that
>
Having read all these docs I now know what all the options are, but I
still don't really know what I should write. I think an example or two
of real world usage would be helpful.
Here I picked some code fragments to help you understand this,
I meant an example or two in the documentation.
T
On Mon, 2015-06-29 at 17:09 +0100, Anthony PERARD wrote:
> On Mon, Jun 29, 2015 at 03:51:57PM +0100, Ian Campbell wrote:
> > On Mon, 2015-06-29 at 15:23 +0100, Anthony PERARD wrote:
> > > OK. What about:
> >
> > I'm afraid none of that really explains why QEMU taking >10s is
> > reasonable/expect
On 2015/6/25 20:31, Ian Jackson wrote:
Tiejun Chen writes ("[v4][PATCH 11/19] tools: introduce some new parameters to set
rdm policy"):
This patch introduces user configurable parameters to specify RDM
resource and according policies,
...
Global RDM parameter, "type", allows user to specify r
On 06/26/2015 07:16 PM, wei.l...@citrix.com wrote:
(Note, please trim your quotes when replying, and also trim the CC list if
necessary. You might also consider changing the subject line of your reply to
"Status of FOO (Was: Xen 4.6 Development Update (X months reminder)")
[...]
== Xen toolst
> -Original Message-
> From: Dario Faggioli [mailto:dario.faggi...@citrix.com]
> Sent: Tuesday, June 30, 2015 10:52 AM
> To: Wu, Feng
> Cc: k...@xen.org; jbeul...@suse.com; andrew.coop...@citrix.com; Tian,
> Kevin; Zhang, Yang Z; george.dun...@eu.citrix.com; Wu, Feng; xen-devel
> Subject:
On Mon, 2015-06-29 at 18:36 +0100, Andrew Cooper wrote:
>
> The basic idea here is:
> 1. When vCPU's state is RUNSTATE_running,
> - set 'NV' to 'Notification Vector'.
> - Clear 'SN' to accpet PI.
> - set 'NDST' to the right pCPU.
> 2. When vCPU's state is RUNSTATE_blocked,
So, first of all, thanks Andrew for drawing my attention on this...
On Mon, 2015-06-29 at 18:35 +0100, Andrew Cooper wrote:
--
Dario Faggioli
Citrix Inc.
> This patch includes the following aspects:
> - Add a global vector to wake up the blocked vCPU
> when an interrupt is being posted to it (
On Mon, 2015-06-29 at 16:32 +0100, Andrew Cooper wrote:
> On 24/06/15 06:18, Feng Wu wrote:
> > diff --git a/xen/arch/x86/hvm/vmx/vmcs.c b/xen/arch/x86/hvm/vmx/vmcs.c
> > index 3aff365..11dc1b5 100644
> > --- a/xen/arch/x86/hvm/vmx/vmcs.c
> > +++ b/xen/arch/x86/hvm/vmx/vmcs.c
> > @@ -40,6 +40,7 @@
+B is about how to handle conflict between reserving reserved device
+memory and guest address space. "strict" means an unsolved conflict leads to
+immediate VM crash, while "relaxed" allows VM moving forward with a warning
+message thrown out. Here "strict" is default.
Surely it would be better
> -Original Message-
> From: xen-devel-boun...@lists.xen.org
> [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of Andrew Cooper
> Sent: Tuesday, June 30, 2015 12:05 AM
> To: Wu, Feng; xen-devel@lists.xen.org
> Cc: Zhang, Yang Z; george.dun...@eu.citrix.com; Tian, Kevin; k...@xen.org;
>
> -Original Message-
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Monday, June 29, 2015 11:41 PM
> To: Wu, Feng; xen-devel@lists.xen.org
> Cc: Tian, Kevin; k...@xen.org; george.dun...@eu.citrix.com;
> jbeul...@suse.com; Zhang, Yang Z
> Subject: Re: [Xen-devel] [v3 08/1
> -Original Message-
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Monday, June 29, 2015 11:33 PM
> To: Wu, Feng; xen-devel@lists.xen.org
> Cc: k...@xen.org; jbeul...@suse.com; Tian, Kevin; Zhang, Yang Z;
> george.dun...@eu.citrix.com; Dario Faggioli
> Subject: Re: [v3
>>> On 6/29/2015 at 06:52 PM, in message
<21905.9050.452111.208...@mariner.uk.xensource.com>, Ian Jackson
wrote:
> Chun Yan Liu writes ("Re: [PATCH V5 2/7] libxl_read_file_contents: add new
> entry to read sysfs file"):
> > On 6/26/2015 at 09:05 PM, in message
> > <21901.20009.85407.581...@
flight 58973 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58973/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds 11 guest-start fail REGR. vs. 58964
test-amd64-i386-libvirt-xsm
flight 58972 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58972/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 58963
test-amd64-i386-xl-qemuu-win7-amd64 1
flight 58971 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58971/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs. 58966
Regre
During init time we treat the dev.config area as a cache
of the host view. However during execution time we treat it
as guest view (by the generic PCI API). We need to sync Xen's
code to the generic PCI API view. This is the first step
by replacing all of the code that uses dev.config or
pci_get_[b
This way we can call it if we fail during init.
This code movement introduces no changes.
Signed-off-by: Konrad Rzeszutek Wilk
---
hw/xen/xen_pt.c | 119 +---
1 file changed, 62 insertions(+), 57 deletions(-)
diff --git a/hw/xen/xen_pt.c b/hw
It should never happen, but in case it does we want to
report. The code will only write up to reg->size so there
is no runtime danger.
Signed-off-by: Konrad Rzeszutek Wilk
---
hw/xen/xen_pt_config_init.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/hw/xen/xen_pt_co
We seem to only use these functions when de-activating the
MSI - so just log errors.
Signed-off-by: Konrad Rzeszutek Wilk
---
hw/xen/xen_pt_msi.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/hw/xen/xen_pt_msi.c b/hw/xen/xen_pt_msi.c
index 5822df5..e3d71
and if we have failures we call xen_pt_destroy introduced in
'xen/pt: Move bulk of xen_pt_unregister_device in its own routine.'
and free all of the allocated structures.
Signed-off-by: Konrad Rzeszutek Wilk
---
hw/xen/xen_pt.c | 32 +---
1 file changed, 21 insertions
To deal with xen_host_pci_[set|get]_ functions returning error values
and clearing ourselves in the init function we should make the
.exit (xen_pt_unregister_device) function be idempotent in case
the generic code starts calling .exit (or for fun does it before
calling .init!).
Signed-off-by: Konr
Hey,
This patchset is dependent on
http://lists.xen.org/archives/html/xen-devel/2015-06/msg04812.html
(Cleanups + various fixes due to libxl ABI + more logging on errors.).
During the discussion of
http://lists.xen.org/archives/html/xen-devel/2015-06/msg01504.html
"[PATCH QEMU-XEN] xen/pt: Sta
For a passthrough device we maintain a state of emulated
registers value contained within d->config. We also consult
the host registers (and apply ro and write masks) whenever
the guest access the registers. This is done in xen_pt_pci_write_config
and xen_pt_pci_read_config.
Also in this picture w
To help with troubleshooting in the field.
Signed-off-by: Konrad Rzeszutek Wilk
---
hw/xen/xen_pt_config_init.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/hw/xen/xen_pt_config_init.c b/hw/xen/xen_pt_config_init.c
index bc871c9..62b6a7b 100644
--- a/hw/xen/xen_pt_config_init.c
+
flight 58970 linux-3.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58970/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-win7-amd64 6 xen-boot fail REGR. vs. 30511
Tests which are failing
Signed-off-by: Boris Ostrovsky
---
Changes in v2:
* Replace is_pvh_vcpu() with is_pvh_domain()
* Only check that 32b versions of hypercalls are available in hvm_do_hypercall()
xen/arch/x86/hvm/hvm.c | 31 ++-
1 file changed, 26 insertions(+), 5 deletions(-)
diff --gi
Changes in v2:
* Only set domain's has_32bit_shinfo, not is_32bit_pv. This adds patch 1 that
replaces some of is_pv_32bit_domain()/is_pv_32bit_vcpu()/is_pv_32on64_vcpu()
tests with has_32bit_shinfo().
Note that I only replaced what I thought was necessary to boot the guest.
MCA and tracing
Signed-off-by: Boris Ostrovsky
---
Changes in v2:
* Keep 64-bit initialization, change the mode to 32b if requested
xen/arch/x86/domain.c | 20 ++--
xen/arch/x86/hvm/hvm.c| 15 ++-
xen/arch/x86/hvm/vmx/vmcs.c | 2 +-
xen/arch/x86/hvm/vmx/vmx.c|
In preparation for enabling 32-bit PVH guests replace a number of guest mode's
tests that assume a PV guest with has_32bit_shinfo() that can be applicable to
both PV and PVH guests.
Signed-off-by: Boris Ostrovsky
---
Changes in v2:
* New patch
xen/arch/x86/domain.c | 10 --
xen/arch/x86
Signed-off-by: Boris Ostrovsky
Acked-by: Ian Campbell
---
tools/libxc/xc_dom_x86.c | 32 +++-
1 file changed, 15 insertions(+), 17 deletions(-)
diff --git a/tools/libxc/xc_dom_x86.c b/tools/libxc/xc_dom_x86.c
index 920fe42..43e79f4 100644
--- a/tools/libxc/xc_dom_x86
As I am in the process of syncing the 'dev.config' and Xen's internal
cache of the PCI config space I noticed that some oddities
in the code and figured that having them in would be easier
for me (so I don't have to handle 20 odd patches).
These:
[PATCH RFC 1/6] xen/pt: Update comments with prope
It has changed but the comments still refer to the old names.
Signed-off-by: Konrad Rzeszutek Wilk
---
hw/xen/xen_pt.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/xen/xen_pt.c b/hw/xen/xen_pt.c
index ed5fcae..706e3d9 100644
--- a/hw/xen/xen_pt.c
+++ b/hw/xen/xen_pt
As we do not use it outside our code.
Signed-off-by: Konrad Rzeszutek Wilk
---
hw/xen/xen_pt.h | 1 -
hw/xen/xen_pt_msi.c | 2 +-
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/hw/xen/xen_pt.h b/hw/xen/xen_pt.h
index 393f36c..09358b1 100644
--- a/hw/xen/xen_pt.h
+++ b/hw/xen/x
We would like to know what the MSI register value is to help
in troubleshooting in the field. As such modify the logging
logic to include such details in xen_pt_msgctrl_reg_write.
Signed-off-by: Konrad Rzeszutek Wilk
---
hw/xen/xen_pt_config_init.c | 6 +++---
1 file changed, 3 insertions(+), 3
When debugging issues that caused the emulator to kill itself
or skipping certain operations (unable to write to host
registers) an stack trace will most definitly aid in debugging
the problem.
As such this patch uses the most basic backtrace to print out
details.
Signed-off-by: Konrad Rzeszutek
However the init routines assume that on errors the return
code is -1 (as the libxc API is) - while those xen_host_* routines follow
another paradigm - negative errno on return, 0 on success.
Signed-off-by: Konrad Rzeszutek Wilk
---
hw/xen/xen_pt.c | 2 +-
1 file changed, 1 insertion(+), 1 delet
In Xen 4.6 commit cd2f100f0f61b3f333d52d1737dd73f02daee592
"libxc: Fix do_memory_op to return negative value on errors"
made the libxc API less odd-ball: On errors, return value is
-1 and error code is in errno. On success the return value
is either 0 or an positive value.
Since we could be runnin
flight 58969 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58969/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-multivcpu 15 guest-start/debian.repeat fail REGR. vs. 58451
Tests which are
Julien Grall wrote:
> Hi,
>
> I tried to run the latest Linux tree
> (4a10a91756ef381bced7b88cfb9232f660b92d93) as DOM0 Xen.
> After destroying a guest using network, I got the following
> lines in the DOM0 kernel log:
>
> unregister_netdevice: waiting for vif1.0 to become free. Usage count = 1
On Thu, 25 Jun 2015, Ian Campbell wrote:
> On Wed, 2015-06-10 at 11:09 +0100, Stefano Stabellini wrote:
> > Change the QEMU xenstore watch path to
> > /local/domain/$LIBXL_TOOLSTACK_DOMID/device-model/$DOMID/$EMULATOR_ID.
>
> This and the next patch should both be changing the xenstore-paths doc
>
On Thu, 25 Jun 2015, Ian Campbell wrote:
> On Wed, 2015-06-10 at 11:09 +0100, Stefano Stabellini wrote:
> > Check whether QEMU supports the xsrestrict option, by parsing its --help
> > output. Store the result on xenstore for future reference on a per QEMU
> > binary basis, so that device_model_ove
On Thu, 25 Jun 2015, Ian Campbell wrote:
> On Tue, 2015-06-16 at 16:39 +0100, Stefano Stabellini wrote:
> > On Tue, 16 Jun 2015, Wei Liu wrote:
> > > On Wed, Jun 10, 2015 at 11:09:50AM +0100, Stefano Stabellini wrote:
> > > > When QEMU restricts its xenstore connection, it cannot provide PV
> > > >
On 06/26/2015 03:35 PM, Ed White wrote:
> On 06/26/2015 12:24 PM, Daniel De Graaf wrote:
>> On 06/22/2015 02:56 PM, Ed White wrote:
>>> From: Ravi Sahita
>>>
>>> Signed-off-by: Ravi Sahita
>>
>> One comment, below.
>>
>> [...]
>>> diff --git a/tools/flask/policy/policy/modules/xen/xen.if
>>> b/t
On Thu, 25 Jun 2015, Ian Campbell wrote:
> On Wed, 2015-06-10 at 11:09 +0100, Stefano Stabellini wrote:
> > The device model is going to restrict its xenstore connection to $DOMID
> > level.
>
> Am I correct in concluding that only oxenstored supports XS_RESTRICT? I
> don't see it in C xenstored a
On 06/26/2015 03:35 PM, Ed White wrote:
On 06/26/2015 12:24 PM, Daniel De Graaf wrote:
On 06/22/2015 02:56 PM, Ed White wrote:
From: Ravi Sahita
Signed-off-by: Ravi Sahita
One comment, below.
[...]
diff --git a/tools/flask/policy/policy/modules/xen/xen.if
b/tools/flask/policy/policy/mod
On Tue, 16 Jun 2015, Wei Liu wrote:
> On Wed, Jun 10, 2015 at 11:09:49AM +0100, Stefano Stabellini wrote:
> > The device model is going to restrict its xenstore connection to $DOMID
> > level. Let qemu-xen access
> > /local/domain/$LIBXL_TOOLSTACK_DOMID/device-model/$DOMID, as it is
> > required by
Most of this series is improvements to html and email output. It
includes the push gate age query library function I offered to Ian
Campbell.
Also thrown in is a patch ot test the Linux 4.1 stable branch.
Ian.
___
Xen-devel mailing list
Xen-devel@list
The fallback entry in the worstrow search, used when a job has not
been run at all, was wrong. Also, fix the doc comment which induced
the mistake.
Signed-off-by: Ian Jackson
---
sg-report-flight |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/sg-report-flight b/sg-re
These show up as leaked processes `[loop1]' etc. too, but that is an
implementation detail, and it is clearer to show them separately.
Signed-off-by: Ian Jackson
---
ts-leak-check |9 +
1 file changed, 9 insertions(+)
diff --git a/ts-leak-check b/ts-leak-check
index fdade36..8a97971
The kernel.org stable git branch layout is the same for 4.1 as for
3.x, so simply extend the pattern, and add the branch to BRANCHES.
DEPLOYMENT NOTE: After this patch is acked, but just before it is
pushed to pretest, run (this version of)
./mg-branch-setup linux-4.1 bisect b953c0d234bc72e8489d
The global $limit was erroneously shadowed by a local in
processjobbranch. Fix this, and move the erroneously hardcoded value
to the global default.
No functional change if --limit was not specified, which it is not for
any of our runs with the in-tree configs.
Signed-off-by: Ian Jackson
---
s
This will allow us to change the function's API in one place (plus all
the call sites).
No functional change in this patch.
Signed-off-by: Ian Jackson
---
Osstest/Executive.pm | 21 +
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git a/Osstest/Executive.pm b/Oss
Previously we produced Summary, and the call sites were confused about
whether it had already been html-escaped. Now we produce something
which is explicitly already html.
No functional change except that some sg-report-host-history output is
escaped as it ought to have been (but this is only rel
This includes the bgcolour attribute name and the quotes. This will
make it possible for this function to sometimes not set a background
for the whole table cell in the future (which will be part of putting
multiple step results in each cell).
No functional change.
Signed-off-by: Ian Jackson
--
Using report_blessingscond instead of the open-coded map.
Signed-off-by: Ian Jackson
---
sg-report-job-history |7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/sg-report-job-history b/sg-report-job-history
index a932c78..31b8d37 100755
--- a/sg-report-job-history
+++
The returned SQL is a self-contained expression, and does not require
additional bind parameters. To spot SQL quoting problems, we die if
a blessing is not reasonable.
The use sites of the $blessingcond in sg-report-flight are adjusted to
no longer pass @blessings to execute.
No overall function
We can't use report_blessingscond because we handle blessings
differently in sg-report-host-history (since we want the history of
even adhoc etc. flights).
Signed-off-by: Ian Jackson
---
sg-report-host-history |6 ++
1 file changed, 6 insertions(+)
diff --git a/sg-report-host-history b/
This adds something like this (would have appeared in 37638):
Last test of basis37629 2015-06-24 21:36:10 Z4 days
Testing same since37635 2015-06-28 03:05:56 Z1 days4 attempts
Failing since 37630 2015-06-26 10:35:44 Z3 days9 attempts
or this (would hav
This utility function provides information about how far behind the
push gate is right now.
I have tested it with this rune in the Cambridge instance:
perl -we 'use Osstest::Executive; use Osstest; use Data::Dumper; open DEBUG,
">&STDERR" or die $!; csreadconfig(); print Dumper
report_find_pu
In report_run_getinfo, used by sg-report-job-history and
sg-report-host-history, make provision for reporting multiple failed
steps.
The failed steps are put side by side (in a single table cell). The
cell background is set by the job status, but the individual steps may
vary their colour, as see
On Thu, 25 Jun 2015, Ian Campbell wrote:
> On Mon, 2015-06-01 at 17:46 +0100, Stefano Stabellini wrote:
> > Try to use "xen-qemudepriv-$domname" first, then
> > "xen-qemudepriv-domid$domid", finally "xen-qemudepriv-shared" and root
> > if everything else fails.
> >
> > The uids need to be manually
On 24/06/15 06:18, Feng Wu wrote:
> This patch includes the following aspects:
> - Add a global vector to wake up the blocked vCPU
> when an interrupt is being posted to it (This
> part was sugguested by Yang Zhang ).
> - Adds a new per-vCPU tasklet to wakeup the blocked
> vCPU. It can be use
On Mon, 2015-06-29 at 21:17 +0530, Vijay Kilari wrote:
> On Mon, Jun 29, 2015 at 9:13 PM, Vijay Kilari wrote:
> > On Mon, Jun 29, 2015 at 5:09 PM, Ian Campbell
> > wrote:
> >> On Mon, 2015-06-22 at 17:31 +0530, vijay.kil...@gmail.com wrote:
> >> [...]
> >>> +/*
> >>> + * ITS command descriptors
On 24/06/15 06:18, Feng Wu wrote:
> When guest changes its interrupt configuration (such as, vector, etc.)
> for direct-assigned devices, we need to update the associated IRTE
> with the new guest vector, so external interrupts from the assigned
> devices can be injected to guests without VM-Exit.
On Mon, 2015-06-29 at 17:45 +0200, Vitaly Kuznetsov wrote:
> 'pfn' and 'start_pfn' are ambiguous, both these functions expect GFNs as
> input.
>
> On x86 the interface of p2m_set_mem_access() in p2m.c doesn't match the
> declaration in p2m-common.h as 'pfn' is being used instead of 'start_pfn'.
>
On Thu, 2015-06-25 at 14:25 +0800, Yang Hongyang wrote:
> Secondary vm is running in colo mode. So we will do
> the following things again and again:
> 1. suspend both primay vm and secondary vm
> 2. sync the state
> 3. resume both primary vm and secondary vm
> We will send qemu's state each time i
On Thu, 2015-06-25 at 14:25 +0800, Yang Hongyang wrote:
> Pass checkpointed_stream from libxl to libxc.
Hrm, so now we seem to have a purely libxl internal usage of this new
enum, but still nothing crossing the libxl.h boundary. I suspect I've
missed something!
> It won't affact legacy migration
On Thu, 2015-06-25 at 14:25 +0800, Yang Hongyang wrote:
> introduce enum type libxl_checkpointed_stream in IDL.
> rename the last argument of migrate_receive from "remus" to
> "checkpointed" since the semantics of this parameter has
> changed.
I don't see anything here which is hitting the libxl A
On Thu, 2015-06-25 at 14:25 +0800, Yang Hongyang wrote:
> From: Wen Congyang
>
> 1. suspend
> a. PVHVM and PV: we use the same way to suspend the guest(send the suspend
space between "guest" and the open parenthesis please.
>request to the guest). If the guest doesn't support evtchn, the xe
On 06/29/2015 06:03 AM, Andrew Cooper wrote:
> On 26/06/15 17:30, Ed White wrote:
>> On 06/24/2015 11:19 AM, Andrew Cooper wrote:
>>> On 24/06/15 18:47, Ed White wrote:
>> This looks like some hoop jumping around the assertions in
>> domain_pause() and vcpu_pause().
>>
>> We should
On 06/29/2015 06:00 AM, Andrew Cooper wrote:
> On 26/06/15 22:17, Ed White wrote:
>> On 06/24/2015 03:29 AM, Andrew Cooper wrote:
>>> On 22/06/15 19:56, Ed White wrote:
diff --git a/xen/include/asm-x86/hvm/vcpu.h
b/xen/include/asm-x86/hvm/vcpu.h
index 3d8f4dc..a1529c0 100644
--
On 24/06/15 06:18, Feng Wu wrote:
> This patch adds an API which is used to update the IRTE
> for posted-interrupt when guest changes MSI/MSI-X information.
>
> Signed-off-by: Feng Wu
> ---
> v3:
> - Remove "adding PDA_MASK()" when updating 'pda_l' and 'pda_h' for IRTE.
> - Change the return type
flight 58966 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58966/
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. vs. 5
On 06/29/2015 08:03 AM, George Dunlap wrote:
> On Mon, Jun 29, 2015 at 3:31 PM, Andrew Cooper
> wrote:
>> On 29/06/15 15:20, George Dunlap wrote:
>>> On Mon, Jun 22, 2015 at 7:56 PM, Ed White wrote:
In preparation for selectively enabling #VE in a later patch, set
suppress #VE on all EP
On Mon, Jun 29, 2015 at 3:31 PM, Andrew Cooper
wrote:
> On 29/06/15 15:20, George Dunlap wrote:
>> On Mon, Jun 22, 2015 at 7:56 PM, Ed White wrote:
>>> In preparation for selectively enabling #VE in a later patch, set
>>> suppress #VE on all EPTE's.
>>>
>>> Suppress #VE should always be the de
On 06/29/2015 06:45 PM, Vitaly Kuznetsov wrote:
> 'pfn' and 'start_pfn' are ambiguous, both these functions expect GFNs as
> input.
>
> On x86 the interface of p2m_set_mem_access() in p2m.c doesn't match the
> declaration in p2m-common.h as 'pfn' is being used instead of 'start_pfn'.
>
> On ARM
On Mon, Jun 29, 2015 at 03:51:57PM +0100, Ian Campbell wrote:
> On Mon, 2015-06-29 at 15:23 +0100, Anthony PERARD wrote:
> > On Fri, Jun 26, 2015 at 05:41:07PM +0100, Ian Campbell wrote:
> > > On Fri, 2015-06-26 at 12:57 +0100, Anthony PERARD wrote:
> > > > On a busy host, QEMU may take more than 1
On 06/29/15 10:54, Andrew Cooper wrote:
On 28/06/15 00:27, Don Slutz wrote:
From: Don Slutz
Also added missing TRAP_DEBUG & VLAPIC.
Signed-off-by: Don Slutz
Acked-by: Ian Campbell
CC: Don Slutz
---
v12:
Switch VMPORT_IGNORED to port, regs->_eax.
v11:
No change
v10:
Added Acked-b
On Thu, 2015-06-25 at 14:25 +0800, Yang Hongyang wrote:
ITYM "handling" in the subject. And perhaps "change" rather than "fix"?
> If the err is RECORD_NOT_PROCESSED, and it is an optional record,
> restore will still fail. There're two options to fix this,
> a, setting rc to 0 when it is an opt
On 24/06/15 06:18, Feng Wu wrote:
> diff --git a/xen/drivers/passthrough/vtd/iommu.h
> b/xen/drivers/passthrough/vtd/iommu.h
> index e807253..49daa70 100644
> --- a/xen/drivers/passthrough/vtd/iommu.h
> +++ b/xen/drivers/passthrough/vtd/iommu.h
> @@ -289,29 +289,43 @@ struct dma_pte {
> /* interr
On Thu, 2015-06-25 at 14:25 +0800, Yang Hongyang wrote:
[...]
> switch (type) {
> case LIBXL_DOMAIN_TYPE_HVM: {
> dss->hvm = 1;
> +dsps->hvm = 1;
> break;
> }
> case LIBXL_DOMAIN_TYPE_PV:
> dss->hvm = 0;
> +dsps->hvm = 0;
> bre
Hi,
I tried to run the latest Linux tree
(4a10a91756ef381bced7b88cfb9232f660b92d93) as DOM0 Xen.
After destroying a guest using network, I got the following
lines in the DOM0 kernel log:
unregister_netdevice: waiting for vif1.0 to become free. Usage count = 1
The bisector pointed the problem aft
On 29/06/15 16:45, Vitaly Kuznetsov wrote:
> 'pfn' and 'start_pfn' are ambiguous, both these functions expect GFNs as
> input.
>
> On x86 the interface of p2m_set_mem_access() in p2m.c doesn't match the
> declaration in p2m-common.h as 'pfn' is being used instead of 'start_pfn'.
>
> On ARM both p2
On Thu, 2015-06-25 at 14:25 +0800, Yang Hongyang wrote:
> This is purely code motion.
On that basis:
>
> Signed-off-by: Yang Hongyang
Acked-by: Ian Campbell
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
On Thu, 2015-06-25 at 14:25 +0800, Yang Hongyang wrote:
> Do the following things:
> - There are 2 checkpoint callbacks, rename them to:
> libxl__remus_domain_{save/restore}_checkpoint_callback
> - Moving remus callbacks into libxl_remus.c, export following
> callbacks for internal use:
> * l
On Mon, Jun 29, 2015 at 9:13 PM, Vijay Kilari wrote:
> On Mon, Jun 29, 2015 at 5:09 PM, Ian Campbell wrote:
>> On Mon, 2015-06-22 at 17:31 +0530, vijay.kil...@gmail.com wrote:
>> [...]
>>> +/*
>>> + * ITS command descriptors - parameters to be encoded in a command
>>> + * block.
>>> + */
>>> +str
flight 58967 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/58967/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-xsm 11 guest-start fail REGR. vs. 58842
Regressions which are reg
'pfn' and 'start_pfn' are ambiguous, both these functions expect GFNs as input.
On x86 the interface of p2m_set_mem_access() in p2m.c doesn't match the
declaration in p2m-common.h as 'pfn' is being used instead of 'start_pfn'.
On ARM both p2m_set_mem_access and p2m_get_mem_access interfaces don't
On Thu, 2015-06-25 at 14:25 +0800, Yang Hongyang wrote:
> move domain resume code into libxl_dom_suspend.c.
> pure code motion except for making
> libxl__domain_resume_device_model() static.
>
> Signed-off-by: Yang Hongyang
Acked-by: Ian Campbell
On Thu, 2015-06-25 at 14:25 +0800, Yang Hongyang wrote:
> Rename libxl__domain_suspend() to libxl__domain_save() since it
> actually do the save domain work.
In response to Ian J's query on the last version Andrew said:
The terminology used by libxc is more consistent in this area
On Mon, Jun 29, 2015 at 5:09 PM, Ian Campbell wrote:
> On Mon, 2015-06-22 at 17:31 +0530, vijay.kil...@gmail.com wrote:
> [...]
>> +/*
>> + * ITS command descriptors - parameters to be encoded in a command
>> + * block.
>> + */
>> +struct its_cmd_desc {
>> +union {
>> +struct {
>> +
1 - 100 of 199 matches
Mail list logo
