flight 124266 xen-4.10-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124266/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 7 xen-boot fail REGR. vs. 123389
test-amd64-amd
On 06/16/2018 12:07 AM, Boris Ostrovsky wrote:
On 06/15/2018 02:50 AM, Oleksandr Andrushchenko wrote:
On 06/15/2018 09:46 AM, Juergen Gross wrote:
On 15/06/18 08:32, Oleksandr Andrushchenko wrote:
Please note, that this will need a change (attached) while
applying to the mainline kernel becaus
Boris, Juergen!
Thank you so much for your comments and time spent on this
series. Appreciate that very much!
Thank you,
Oleksandr
On 06/15/2018 09:27 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
This work is in response to my previous attempt to introduce Xen/DRM
zero-co
On 06/18/2018 09:07 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Dan Carpenter has reported that there is the following static checker
warning:
drivers/gpu/drm/drm_prime.c:317 drm_gem_map_dma_buf()
warn: 'sgt' can also be NULL
314 sgt = obj->dev->driver-
From: Oleksandr Andrushchenko
Dan Carpenter has reported that there is the following static checker
warning:
drivers/gpu/drm/drm_prime.c:317 drm_gem_map_dma_buf()
warn: 'sgt' can also be NULL
314 sgt = obj->dev->driver->gem_prime_get_sg_table(obj);
315
316 if (!IS_ERR(sgt
This run is configured for baseline tests only.
flight 74883 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74883/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf dde2dd64f07041c2ccc23dc7a5a846e667b7bb1a
baseline v
This run is configured for baseline tests only.
flight 74882 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74882/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemuu-win10-i386 10 windows-install f
Hi Stefano,
On 06/13/2018 11:15 PM, Stefano Stabellini wrote:
Make vpl011 being able to be used without a userspace component in Dom0.
In that case, output is printed to the Xen serial and input is received
from the Xen serial one character at a time.
Call domain_vpl011_init during construct_do
Hi Stefano,
On 06/14/2018 10:15 PM, Stefano Stabellini wrote:
On Thu, 14 Jun 2018, Julien Grall wrote:
On 13/06/18 23:15, Stefano Stabellini wrote:
Move a few constants defined by libxl_arm.c to
xen/include/public/arch-arm.h, so that they are together with the other
guest related #defines such
On 06/13/2018 11:15 PM, Stefano Stabellini wrote:
Introduce support for the "xen,domU" compatible node on device tree.
Create new DomU VMs based on the information found on device tree under
"xen,domU".
While I like the idea of having multiple domain created by Xen, I think
there are still f
Hi Stefano,
On 06/15/2018 12:35 AM, Stefano Stabellini wrote:
On Thu, 14 Jun 2018, Julien Grall wrote:
On 13/06/18 23:15, Stefano Stabellini wrote:
-
-printk("*** LOADING DOMAIN 0 ***\n");
-if ( dom0_mem <= 0 )
-{
-warning_add("PLEASE SPECIFY dom0_mem PARAMETER - USING 512M
Hi Stefano,
On 06/13/2018 11:15 PM, Stefano Stabellini wrote:
Introduce vpl011 support to guests started from Xen: it provides a
simple way to print output from a guest, as most guests come with a
pl011 driver. It is also able to provide a working console with
interrupt support.
Signed-off-by:
flight 124248 xen-4.9-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124248/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-localmigrate/x10 fail REGR. vs.
124043
test-armh
flight 124209 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124209/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-rtds broken
test-armhf-armhf-xl
flight 124233 linux-4.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124233/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-xsm 6 xen-install fail REGR. vs. 124110
Tests which did not
flight 124243 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124243/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf dde2dd64f07041c2ccc23dc7a5a846e667b7bb1a
baseline version:
ovmf a05a8a5aa17da4bc71447
flight 124232 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124232/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stopfail like 124199
test-armhf-armhf-libvirt 14 sav
flight 124239 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124239/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 123814
build-i386-libvirt
From: Joshua Otto
In preparation for the addition of a mem paging op with different
arguments than the existing ops, move the op-specific arguments into a
union.
No functional change.
Signed-off-by: Joshua Otto
---
tools/libxc/xc_mem_paging.c | 8
xen/arch/x86/mm/mem_paging.c | 6
From: Joshua Otto
Hi,
A little over a year ago, I posted a patch series implementing support for
post-copy live migration via xenpaging [1]. Following Andrew and Wei's review
of the initial refactoring patches, I promised to follow up with revised
patches, a design document and an experimental
From: Joshua Otto
When processing a PAGE_DATA record, the restore code:
1) applies a number of sanity checks on the record's headers and size
2) decodes the list of packed page info into pfns and their types
3) using the pfn and type info, populates and fills the pages into the
guest using pro
From: Joshua Otto
Right now, write_split_record() - which is delegated to by
write_record() - implicitly writes to ctx->fd. This means it can't be
used with the restore context's send_back_fd, which is inconvenient.
Add an 'fd' parameter to both write_record() and write_split_record(),
and mech
From: Joshua Otto
Both xc_domain_save() and xc_domain_restore() have a high number of
parameters, including a number of boolean parameters that are split
between a bitfield flags argument and separate individual boolean
arguments. Further, many of these arguments are dead/ignored.
Tidy the inte
From: Joshua Otto
Add the receive-side logic for a new 'postcopy' phase in the live
migration algorithm.
To support this migration phase:
- Augment the main restore record-processing logic to recognize and
handle the postcopy-initiation records.
- Add the core logic for the phase, postcopy_res
From: Joshua Otto
- Add a 'memory_strategy' parameter to libxl_domain_live_migrate(),
which specifies how the remainder of the memory migration should be
approached after the iterative precopy phase is completed.
- Plug this parameter into the libxl migration precopy policy
implementation.
From: Joshua Otto
Teach send_checkpoint_dirty_pfn_list() to use write_record()'s new fd
parameter, avoiding the need for a manual writev().
No functional change.
Signed-off-by: Joshua Otto
Acked-by: Wei Liu
Reviewed-by: Andrew Cooper
---
tools/libxc/xc_sr_restore.c | 27
From: Joshua Otto
To make the libxl receiver capable of supporting postcopy live
migration:
- As was done for the libxl stream writer, add a symmetric callback
chain through the stream reader that reads the sequence of xl records
necessary to resume the guest and enter the postcopy phase. Th
From: Joshua Otto
To write guest pages into the stream, the save logic builds up batches
of pfns to be written and performs all of the work necessary to write
them whenever a full batch has been accumulated. Writing a PAGE_DATA
batch entails determining the types of all pfns in the batch, mappin
From: Joshua Otto
In write_batch() on the migration save side and in process_page_data()
on the corresponding path on the restore side, a local variable named
'mfns' is used to refer to an array of what are actually gfns. Rename
both to 'gfns' to address this.
No functional change.
Signed-off-
From: Joshua Otto
- allocate the new postcopy record type numbers
- augment the stream format specification to include these new types and
their role in the protocol
Signed-off-by: Joshua Otto
---
docs/specs/libxc-migration-stream.pandoc | 175 +++
tools/libxc/xc_
From: Joshua Otto
The precopy phase of the xc_domain_save() live migration algorithm has
historically been implemented to run until either a) (almost) no pages
are dirty or b) some fixed, hard-coded maximum number of precopy
iterations has been exceeded. This policy and its implementation are
le
From: Joshua Otto
The paging API presently permits only individual, populated pages to be
evicted, and even then only after a previous nomination op on the
candidate page. This works well at steady-state, but is somewhat
awkward and inefficient for pagers attempting to implement startup
demand-p
From: Joshua Otto
There are three callback chains through libxl_stream_write: the 'normal'
straight-through save path initiated by libxl__stream_write_start(), the
iterated checkpoint path initiated each time by
libxl__stream_write_start_checkpoint(), and the (short) back-channel
checkpoint path
From: Joshua Otto
Enable non-blocking migration record reads by adding a helper routine that
manages the context of a record read across multiple invocations as the record's
data becomes available over time.
Signed-off-by: Joshua Otto
---
tools/libxc/xc_private.c | 21 +++
tools/
From: Joshua Otto
The PAGE_DATA migration record type is specified as an array of
uint64_ts encoding pfns and their types, followed by an array of page
contents. Postcopy live migration specifies a number of records with
similar or the same format, and it would be convenient to be able to
re-use
From: Joshua Otto
The libxc migration stream specification document asserts that, within
an hvm migration stream, "HVM_PARAMS must precede HVM_CONTEXT, as
certain parameters can affect the validity of architectural state in the
context." This sounds reasonable, but the in-tree implementation of
From: Joshua Otto
As the previous patch did for libxl_stream_write, do for
libxl_stream_read. libxl_stream_read already has a notion of phase for
its record-buffering behaviour - this is combined with the callback
chain phase. Again, this is done to support the addition of a new
callback chain
From: Joshua Otto
Add a new 'postcopy' phase to the live migration algorithm, during which
unmigrated domain memory is paged over the network on-demand _after_ the
guest has been resumed at the destination.
To do so:
- Add a new precopy policy option, XGS_POLICY_POSTCOPY, that policies
can use
From: Joshua Otto
To make the libxl sender capable of supporting postcopy live migration:
- Add a postcopy transition callback chain through the stream writer (this
callback chain is nearly identical to the checkpoint callback chain, and
differs meaningfully only in its failure/completion beh
From: Joshua Otto
The COLO xc domain save and restore procedures both make use of a 'postcopy'
callback to defer part of each checkpoint operation to xl. In this context, the
name 'postcopy' is meant as "the callback invoked immediately after this
checkpoint's memory callback." This is an unfor
From: Joshua Otto
Permit libxl to implement the xc_domain_save() precopy_policy callback
by adding it to the RPC generation machinery and implementing a policy
in libxl with the same semantics as the old one.
No functional change.
Signed-off-by: Joshua Otto
---
tools/libxc/xc_sr_save.c
From: Joshua Otto
During the transition downtime phase of postcopy live migration, mark
batches of dirty pfns as paged-out using the new populate_evicted()
paging op rather than populating, nominating and evicting each dirty pfn
individually. This significantly reduces downtime during transition
This is a note to let you know that I've just added the patch titled
x86/xen: Reset VCPU0 info pointer after shared_info remap
to the 4.16-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
This is a note to let you know that I've just added the patch titled
x86/xen: Reset VCPU0 info pointer after shared_info remap
to the 4.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
flight 124300 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124300/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen e23d2234e08872ac1c719f3e338994581483440f
baseline version:
xen 4133
Just like in the HVM emulation and EFI runtime call cases we must not
set CR0.TS here in fully eager mode. Note that idle vCPU-s never have
->arch.fully_eager_fpu set (for their initialization not going through
vcpu_init_fpu()), so we won't hit the respective ASSERT() in
vcpu_restore_fpu_eager().
Just like in the HVM emulation case we must not set CR0.TS here in
fully eager mode. Note that idle vCPU-s never have
->arch.fully_eager_fpu set (for their initialization not going through
vcpu_init_fpu()), so we won't hit the respective ASSERT() in
vcpu_restore_fpu_eager().
Introduce a "curr" loc
flight 124225 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124225/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-credit2 7 xen-boot fail REGR. vs. 124090
test-amd64-amd64-x
48 matches
Mail list logo
