>>> On 12.06.18 at 18:29, wrote:
> On 12/06/18 17:00, Manuel Bouyer wrote:
>> On Tue, Jun 12, 2018 at 04:54:30PM +0100, Andrew Cooper wrote:
>>> On 12/06/18 16:38, Manuel Bouyer wrote:
On Tue, Jun 12, 2018 at 01:39:05PM +0200, Manuel Bouyer wrote:
> I applied this patch to 4.11rc4 (let's
On 06/13/2018 04:07 AM, Boris Ostrovsky wrote:
On 06/12/2018 09:41 AM, Oleksandr Andrushchenko wrote:
One more thing: please add a comment here saying that frames array is
array of PFNs (in Xen granularity), which is what
XENMEM_populate_physmap requires. And remove (or update to name the
On 13/06/18 08:11, Jan Beulich wrote:
On 12.06.18 at 17:58, wrote:
>> Trying to reproduce the problem in a limited test environment finally
>> worked: doing a loop of "xl save -c" produced the problem after 198
>> iterations.
>>
>> I have asked a SUSE engineer doing kernel memory management i
On 06/13/2018 09:40 AM, Juergen Gross wrote:
On 13/06/18 08:13, Oleksandr Andrushchenko wrote:
On 06/13/2018 09:11 AM, Dmitry Torokhov wrote:
On June 12, 2018 10:49:31 PM PDT, Oleksandr Andrushchenko
wrote:
On 06/13/2018 02:40 AM, Dmitry Torokhov wrote:
On Tue, Jun 12, 2018 at 03:46:10PM +02
>>> On 12.06.18 at 21:53, wrote:
> On Tue, 12 Jun 2018, Jan Beulich wrote:
>> >> >> As a consequence of these changes, some options will become
>> >> >> user-visible
>> >> >> and not dependent on CONFIG_EXPERT. It does not mean that Xen Project
>> >> >> will security support all possible combinat
On 13/06/18 08:13, Oleksandr Andrushchenko wrote:
> On 06/13/2018 09:11 AM, Dmitry Torokhov wrote:
>> On June 12, 2018 10:49:31 PM PDT, Oleksandr Andrushchenko
>> wrote:
>>> On 06/13/2018 02:40 AM, Dmitry Torokhov wrote:
On Tue, Jun 12, 2018 at 03:46:10PM +0200, Juergen Gross wrote:
> On
>>> On 12.06.18 at 19:40, wrote:
> On 12/06/18 09:27, Jan Beulich wrote:
> On 08.06.18 at 20:48, wrote:
>>> --- a/xen/arch/x86/hvm/vmx/vmcs.c
>>> +++ b/xen/arch/x86/hvm/vmx/vmcs.c
>>> @@ -1452,6 +1452,74 @@ int vmx_add_msr(struct vcpu *v, uint32_t msr,
>>> uint64_t val,
>>> return rc;
>
>>> On 12.06.18 at 18:33, wrote:
> On 12/06/18 10:00, Jan Beulich wrote:
> On 12.06.18 at 10:51, wrote:
>>> On 12/06/2018 09:15, Jan Beulich wrote:
>>> On 08.06.18 at 20:48, wrote:
> @@ -3106,14 +3104,13 @@ static int vmx_msr_write_intercept(unsigned int
> msr,
>
>>> uint64_t
On 06/13/2018 09:25 AM, Dmitry Torokhov wrote:
On June 12, 2018 11:13:40 PM PDT, Oleksandr Andrushchenko
wrote:
On 06/13/2018 09:11 AM, Dmitry Torokhov wrote:
On June 12, 2018 10:49:31 PM PDT, Oleksandr Andrushchenko
wrote:
On 06/13/2018 02:40 AM, Dmitry Torokhov wrote:
On Tue, Jun 12, 20
>>> On 12.06.18 at 21:39, wrote:
> On Tue, 12 Jun 2018, Jan Beulich wrote:
>> >>> On 12.06.18 at 16:10, wrote:
>> > Since qemu-2.10 it is required to unplug emulated devices again after
>> > a live migration. If this is not done, qemu's block-backend driver
>> > will be unable to open the backing
On 06/13/2018 03:47 AM, Boris Ostrovsky wrote:
On 06/12/2018 09:41 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
diff --git a/include/xen/mem-reservation.h
b/include/xen/mem-reservation.h
new file mode 100644
index ..e0939387278d
--- /dev/null
+++ b/include/
On June 12, 2018 11:13:40 PM PDT, Oleksandr Andrushchenko
wrote:
>On 06/13/2018 09:11 AM, Dmitry Torokhov wrote:
>> On June 12, 2018 10:49:31 PM PDT, Oleksandr Andrushchenko
> wrote:
>>> On 06/13/2018 02:40 AM, Dmitry Torokhov wrote:
On Tue, Jun 12, 2018 at 03:46:10PM +0200, Juergen Gross wr
>>> On 12.06.18 at 22:55, wrote:
> On Tue, Jun 12, 2018 at 05:38:45PM +0200, Manuel Bouyer wrote:
>> On Tue, Jun 12, 2018 at 01:39:05PM +0200, Manuel Bouyer wrote:
>> > I applied this patch to 4.11rc4 (let's not change too much things at the
>> > same time) and rebooted my test host. Hopefully I'l
On 06/13/2018 09:11 AM, Dmitry Torokhov wrote:
On June 12, 2018 10:49:31 PM PDT, Oleksandr Andrushchenko
wrote:
On 06/13/2018 02:40 AM, Dmitry Torokhov wrote:
On Tue, Jun 12, 2018 at 03:46:10PM +0200, Juergen Gross wrote:
On 12/06/18 09:48, Oleksandr Andrushchenko wrote:
From: Oleksandr And
On June 12, 2018 10:49:31 PM PDT, Oleksandr Andrushchenko
wrote:
>On 06/13/2018 02:40 AM, Dmitry Torokhov wrote:
>> On Tue, Jun 12, 2018 at 03:46:10PM +0200, Juergen Gross wrote:
>>> On 12/06/18 09:48, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
This is the sync u
>>> On 12.06.18 at 17:58, wrote:
> Trying to reproduce the problem in a limited test environment finally
> worked: doing a loop of "xl save -c" produced the problem after 198
> iterations.
>
> I have asked a SUSE engineer doing kernel memory management if he
> could think of something. His idea i
flight 124110 linux-4.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124110/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-examine4 memdisk-try-append fail in 124086 pass in 124110
test-armhf-armhf-libvirt-raw 5 ho
On 06/13/2018 02:40 AM, Dmitry Torokhov wrote:
On Tue, Jun 12, 2018 at 03:46:10PM +0200, Juergen Gross wrote:
On 12/06/18 09:48, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
This is the sync up with the canonical definitions of the input,
sound and display protocols in Xen.
C
On 06/13/2018 01:07 AM, Dmitry Torokhov wrote:
On Tue, Jun 12, 2018 at 10:48:56AM +0300, Oleksandr Andrushchenko wrote:
+ if (!(with_kbd | with_ptr | with_mtouch)) {
I changed this to logical "OR" and applied, thank you.
Yes, that's better, thank you
+ ret = -ENXIO;
+
Hello,
I am implementing Multiboot2 support for FreeBSD loader to load Xen
kernel. Currently I pass EFI 64-bit system table pointer tag, EFI boot
services not terminated tag, EFI 64-bit image handle pointer tag and
Image load base physical address tag.
The problem is, Xen kernel gets stuck into i
On 06/12/2018 11:04 AM, Eric Blake wrote:
> On 06/12/2018 03:51 PM, Richard Henderson wrote:
>> On 06/10/2018 03:14 PM, Philippe Mathieu-Daudé wrote:
>>> xen_pv_printf(xendev, 1, "type \"%s\", fileproto \"%s\", filename
>>> \"%s\","
>>> - " size %" PRId64 " (%" PRId64 " MB)\n
On 06/10/2018 03:14 PM, Philippe Mathieu-Daudé wrote:
> xen_pv_printf(xendev, 1, "type \"%s\", fileproto \"%s\", filename
> \"%s\","
> - " size %" PRId64 " (%" PRId64 " MB)\n",
> + " size %" PRId64 " (%llu MB)\n",
>blkdev->type, blkdev->fi
flight 124100 xen-4.8-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124100/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-xsm broken in 124070
build-i386-pvops
On 06/12/2018 09:42 AM, Oleksandr Andrushchenko wrote:
int gntdev_dmabuf_imp_release(struct gntdev_dmabuf_priv *priv, u32 fd)
{
- return -EINVAL;
+ struct gntdev_dmabuf *gntdev_dmabuf;
+ struct dma_buf_attachment *attach;
+ struct dma_buf *dma_buf;
+
+ gntdev_
On 06/12/2018 09:41 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
1. Create a dma-buf from grant references provided by the foreign
domain. By default dma-buf is backed by system memory pages, but
by providing GNTDEV_DMA_FLAG_XXX flags it can also be created
as
On 06/12/2018 09:41 AM, Oleksandr Andrushchenko wrote:
diff --git a/drivers/xen/gntdev.c b/drivers/xen/gntdev.c
index a09db23e9663..e82660d81d7e 100644
--- a/drivers/xen/gntdev.c
+++ b/drivers/xen/gntdev.c
@@ -48,6 +48,9 @@
#include
#include "gntdev-common.h"
+#ifdef CONFIG_XEN_GNTDEV
On 06/12/2018 09:41 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
This is in preparation for adding support of DMA buffer
functionality: make map/unmap related code and structures, used
privately by gntdev, ready for dma-buf extension, which will re-use
these. Rename corres
On 06/12/2018 09:41 AM, Oleksandr Andrushchenko wrote:
static void gntdev_print_maps(struct gntdev_priv *priv,
@@ -121,8 +146,27 @@ static void gntdev_free_map(struct grant_map *map)
if (map == NULL)
return;
+#ifdef CONFIG_XEN_GRANT_DMA_ALLOC
+ if (map->d
On 06/12/2018 09:41 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Extend grant table module API to allow allocating buffers that can
be used for DMA operations and mapping foreign grant references
on top of those.
The resulting buffer is similar to the one allocated by the
On 06/12/2018 09:41 AM, Oleksandr Andrushchenko wrote:
One more thing: please add a comment here saying that frames array is
array of PFNs (in Xen granularity), which is what
XENMEM_populate_physmap requires. And remove (or update to name the
actual call you are making) the corresponding c
On 06/12/2018 09:41 AM, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
diff --git a/include/xen/mem-reservation.h b/include/xen/mem-reservation.h
new file mode 100644
index ..e0939387278d
--- /dev/null
+++ b/include/xen/mem-reservation.h
@@ -0,0 +1,64 @@
+/* SPDX-L
On Tue, Jun 12, 2018 at 03:46:10PM +0200, Juergen Gross wrote:
> On 12/06/18 09:48, Oleksandr Andrushchenko wrote:
> > From: Oleksandr Andrushchenko
> >
> > This is the sync up with the canonical definitions of the input,
> > sound and display protocols in Xen.
> >
> > Changes to kbdif:
> > 1. A
From: Juergen Gross
Date: Tue, 12 Jun 2018 08:57:53 +0200
> The max number of slots used in xennet_get_responses() is set to
> MAX_SKB_FRAGS + (rx->status <= RX_COPY_THRESHOLD).
>
> In old kernel-xen MAX_SKB_FRAGS was 18, while nowadays it is 17. This
> difference is resulting in frequent messag
>
> ## Functionality tested
>
> - PV & HVM/ xl create, shu, des
> - HVM/ altp2m with LibVMI and Drakvuf (on the modern hardware only)
Happy to see Drakvuf getting some tests alongside Xen :) This test
report thus covers vm_event and memaccess interfaces as well.
Thanks!
Tamas
___
flight 124093 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124093/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stopfail like 123987
test-armhf-armhf-libvirt 14 sav
Hi Stefano,
On 12/06/2018 20:53, Stefano Stabellini wrote:
On Tue, 12 Jun 2018, Jan Beulich wrote:
As a consequence of these changes, some options will become user-visible
and not dependent on CONFIG_EXPERT. It does not mean that Xen Project
will security support all possible combinations of kc
On Tue, Jun 12, 2018 at 10:48:56AM +0300, Oleksandr Andrushchenko wrote:
>
> + if (!(with_kbd | with_ptr | with_mtouch)) {
I changed this to logical "OR" and applied, thank you.
> + ret = -ENXIO;
> + goto error;
> + }
> +
> ret = xenkbd_connect_backend(dev,
On 12/06/2018 20:41, Stefano Stabellini wrote:
On Tue, 12 Jun 2018, Julien Grall wrote:
Hi,
On 12/06/18 16:55, Stefano Stabellini wrote:
On Tue, 12 Jun 2018, Julien Grall wrote:
Hi Stefano,
On 12/06/18 01:50, Stefano Stabellini wrote:
On Tue, 5 Jun 2018, Julien Grall wrote:
Hi Stefano,
Hi Konrad,
On 12/06/2018 22:17, Konrad Rzeszutek Wilk wrote:
On Tue, Jun 12, 2018 at 12:36:37PM +0100, Julien Grall wrote:
During the MMU setup process, Xen will set SCTLR_EL2.WNX
(Write-Non-eXecutable) bit. Because of that, the alternative code need
to re-mapped the region in a difference plac
flight 124092 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124092/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 123554
test-armhf-armhf-ex
Hello! Here is a success report for 4.11.0 rc6. Better late than never, right?
## Hardware
- modern Lenovo V520-15IKL Desktop (i5-7400: 4 cores)
- old monster IBM 3850 M2 (x4 Xeon X7350: 16 cores)
I wish I had some Opterons available.
## Software (resp.)
- Devuan/ascii and Linux 4.17.0.slack
On Tue, Jun 12, 2018 at 12:36:37PM +0100, Julien Grall wrote:
> During the MMU setup process, Xen will set SCTLR_EL2.WNX
> (Write-Non-eXecutable) bit. Because of that, the alternative code need
> to re-mapped the region in a difference place in order to modify the
> text section.
>
> At the moment
On Tue, Jun 12, 2018 at 08:56:07PM +, Anchal Agarwal wrote:
> Hello,
> I am sending out a series of patches that implements guest
> PM hibernation. These guests are running on xen hypervisor.
> The patches had been tested against mainstream kernel and latest
> xen version-4.11. EC2 instance hib
On 06/12/2018 03:51 PM, Richard Henderson wrote:
On 06/10/2018 03:14 PM, Philippe Mathieu-Daudé wrote:
xen_pv_printf(xendev, 1, "type \"%s\", fileproto \"%s\", filename \"%s\","
- " size %" PRId64 " (%" PRId64 " MB)\n",
+ " size %" PRId64 " (%llu MB)\n",
From: Munehisa Kamata
Add freeze and restore callbacks for PM suspend and hibernation support.
The freeze handler simply disconnects the frotnend from the backend and
frees resources associated with queues after disabling the net_device
from the system. The restore handler just changes the fronte
From: Munehisa Kamata
Add a simple helper function to "shutdown" active PIRQs, which actually
closes event channels but keeps related IRQ structures intact. PM
suspend/hibernation code will rely on this.
Signed-off-by: Munehisa Kamata
Signed-off-by: Anchal Agarwal
Reviewed-by: Munehisa Kamata
From: Munehisa Kamata
Close event channels allocated for devices which are backed by PIRQ and
still active when suspending the system core. Normally, the devices are
emulated legacy devices, e.g. PS/2 keyboard, floppy controller and etc.
Without this, in PM hibernation, information about the eve
From: Munehisa Kamata
Introduce simple functions which help to know the on-going suspend mode
so that other Xen-related code can behave differently according to the
current suspend mode.
Signed-off-by: Munehisa Kamata
Signed-off-by: Anchal Agarwal
Reviewed-by: Alakesh Haloi
Reviewed-by: Sebas
From: Munehisa Kamata
Since commit b3e96c0c7562 ("xen: use freeze/restore/thaw PM events for
suspend/resume/chkpt"), xenbus uses PMSG_FREEZE, PMSG_THAW and
PMSG_RESTORE events for Xen suspend. However, they're actually assigned
to xenbus_dev_suspend(), xenbus_dev_cancel() and xenbus_dev_resume()
From: Munehisa Kamata
Add Xen PVHVM specific system core callbacks for PM suspend and
hibernation support. The callbacks suspend and resume Xen primitives,
like shared_info, pvclock and grant table. Note that Xen suspend can
handle them in a different manner, but system core callbacks are called
From: Munehisa Kamata
To differentiate between Xen suspend, PM suspend and PM hibernation,
keep track of the on-going suspend mode by mainly using a new PM
notifier. Since Xen suspend doesn't have corresponding PM event, its
main logic is modfied to acquire pm_mutex and set the current mode.
Not
From: Munehisa Kamata
Save steal clock values of all present CPUs in the system core ops
suspend callbacks. Also, restore a boot CPU's steal clock in the system
core resume callback. For non-boot CPUs, restore after they're brought
up, because runstate info for non-boot CPUs are not active until
From: Munehisa Kamata
Add freeze and restore callbacks for PM suspend and hibernation support.
The freeze handler stops a block-layer queue and disconnect the frontend
from the backend while freeing ring_info and associated resources. The
restore handler re-allocates ring_info and re-connect to t
From: Munehisa Kamata
Currently, steal time accounting code in scheduler expects steal clock
callback to provide monotonically increasing value. If the accounting
code receives a smaller value than previous one, it uses a negative
value to calculate steal time and results in incorrectly updated i
Introduce a small function which re-uses shared page's PA allocated
during guest initialization time in reserve_shared_info() and not
allocate new page during resume flow.
It also does the mapping of shared_info_page by calling
xen_hvm_init_shared_info() to use the function.
Signed-off-by: Anchal
From: Aleksei Besogonov
The SNAPSHOT_SET_SWAP_AREA is supposed to be used to set the hibernation
offset on a running kernel to enable hibernating to a swap file.
However, it doesn't actually update the swsusp_resume_block variable. As
a result, the hibernation fails at the last step (after all th
Hello,
I am sending out a series of patches that implements guest
PM hibernation. These guests are running on xen hypervisor.
The patches had been tested against mainstream kernel and latest
xen version-4.11. EC2 instance hibernation feature is provided to
the AWS EC2 customers. PM hibernation uses
On Tue, Jun 12, 2018 at 05:38:45PM +0200, Manuel Bouyer wrote:
> On Tue, Jun 12, 2018 at 01:39:05PM +0200, Manuel Bouyer wrote:
> > I applied this patch to 4.11rc4 (let's not change too much things at the
> > same time) and rebooted my test host. Hopefully I'll have some data to
> > report
> > soo
On Tue, 12 Jun 2018, Jan Beulich wrote:
> >> >> As a consequence of these changes, some options will become user-visible
> >> >> and not dependent on CONFIG_EXPERT. It does not mean that Xen Project
> >> >> will security support all possible combinations of kconfig options.
> >> >> Instead, there w
On Tue, 12 Jun 2018, Jan Beulich wrote:
> >>> On 12.06.18 at 16:10, wrote:
> > Since qemu-2.10 it is required to unplug emulated devices again after
> > a live migration. If this is not done, qemu's block-backend driver
> > will be unable to open the backing disk image because it is still busy
> >
On Tue, 5 Jun 2018, Julien Grall wrote:
> The code has been around since the beginning of Xen Arm. However, I am
> not aware of any user and the code is pretty bogus:
> 1) It is assuming virtual address == physical address.
> 2) The cache is not cleaned after the Image is loaded but the Ima
On Tue, 5 Jun 2018, Julien Grall wrote:
> Some of the functions implemented in setup.c are only used at boot but
> not yet marked as such.
>
> Signed-off-by: Julien Grall
Reviewed-by: Stefano Stabellini
> ---
> xen/arch/arm/setup.c | 10 +-
> 1 file changed, 5 insertions(+), 5 deletio
On Tue, 5 Jun 2018, Julien Grall wrote:
> Now that ELF support has been dropped to boot Dom0, no-one is using
> libelf within the hypervisor.
>
> Introduce a config option to select libelf on x86 and keep unselected
> for Arm.
>
> Signed-off-by: Julien Grall
Reviewed-by: Stefano Stabellini
>
On Tue, 12 Jun 2018, Julien Grall wrote:
> Hi,
>
> On 12/06/18 16:55, Stefano Stabellini wrote:
> > On Tue, 12 Jun 2018, Julien Grall wrote:
> > > Hi Stefano,
> > >
> > > On 12/06/18 01:50, Stefano Stabellini wrote:
> > > > On Tue, 5 Jun 2018, Julien Grall wrote:
> > > > > Hi Stefano,
> > > > >
On Tue, 5 Jun 2018, Julien Grall wrote:
> Libfdt is used for:
> - Unflatten the Flatten Device-Tree (FDT) blob
> - Create Device-Tree for the Hardware-Domain
>
> Both use are done during the initialization of Xen. So move all the
> libfdt to init.
>
> Note that the runes was borrowed from
On Tue, 5 Jun 2018, Julien Grall wrote:
> The file kernel.c only contains code/data used during the
> initialization. So move everything to init and mark the file as such.
>
> Signed-off-by: Julien Grall
Reviewed-by: Stefano Stabellini
> ---
> xen/arch/arm/Makefile | 2 +-
> xen/arch/arm/ke
On Tue, 5 Jun 2018, Julien Grall wrote:
> The file domain_build.c only contains code/data used during the
> initialization. So move everything to init and mark the file as such.
>
> Signed-off-by: Julien Grall
Reviewed-by: Stefano Stabellini
> ---
> xen/arch/arm/Makefile | 2 +-
> xen
On Tue, 5 Jun 2018, Julien Grall wrote:
> Dom0 (aka hardware domain on Arm) is always direct mapped. Rather than
> using a global variable to store a const, directly open-code it or
> replace the use with is_domain_direct_mapped(...) macros.
>
> This will also help a follow-up patch to move all do
On 12/06/18 18:40, Andrew Cooper wrote:
> On 12/06/18 09:27, Jan Beulich wrote:
>>> +end = start + total;
>>> +ent = locate_msr_entry(start + substart, start + subend, msr);
>>> +
>>> +if ( (ent == end) || (ent->index != msr) )
>>> +return -ESRCH;
>>> +
>>> +memmove(ent, ent
On 12/06/18 09:27, Jan Beulich wrote:
On 08.06.18 at 20:48, wrote:
>> --- a/xen/arch/x86/hvm/vmx/vmcs.c
>> +++ b/xen/arch/x86/hvm/vmx/vmcs.c
>> @@ -1452,6 +1452,74 @@ int vmx_add_msr(struct vcpu *v, uint32_t msr,
>> uint64_t val,
>> return rc;
>> }
>>
>> +int vmx_del_msr(struct vcpu
flight 124090 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124090/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 124057
Tests which did no
cs-bisection-step assumes that every job it will need to create has a
unique name. Indeed, in general, it is probably not reasonable to
expect it to work if that is not the case.
build-amd64-freebsd needs a previous build-amd64-freebsd.
Currently cs-bisection-step confuses itself into writing a
This is useful for debugging.
Signed-off-by: Ian Jackson
---
Osstest.pm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Osstest.pm b/Osstest.pm
index 2263786..3377ea3 100644
--- a/Osstest.pm
+++ b/Osstest.pm
@@ -330,6 +330,8 @@ sub db_retry ($$$;$$) {
last if $db_retry_stop
Parse the runvar name earlier, adding job and orgflight members to the
row hashes we got from the db. This slightly unifies the call to
preparejob, but more relevantly, makes the effective job and flight
information available earlier. That will be useful in a moment.
No functional change.
Signe
Signed-off-by: Ian Jackson
---
cs-bisection-step | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cs-bisection-step b/cs-bisection-step
index 0be8bd0..0d0e08f 100755
--- a/cs-bisection-step
+++ b/cs-bisection-step
@@ -1208,7 +1208,7 @@ END
if ($cache_option and $cacheok an
When we detect that we are considering a job which is identically
named to one earlier in the dependency chain, it could happen that the
final referencing runvar in the job at which we break the cycle is
actually to an unqualified job name.
(This cannot happen unless the cycle has more than 2 jobs
From: Ian Jackson
Ian Jackson (5):
db_retry: Honour new OSSTEST_DB_ALWAYS_ABORT variable
cs-bisection-step: Improve a message
cs-bisection-step: Refactor $subjobs calculations a bit
cs-bisection-step: Handle build job chains
cs-bisection-step: Do explicitly set runvar for suppressed rec
On 12/06/18 10:00, Jan Beulich wrote:
On 12.06.18 at 10:51, wrote:
>> On 12/06/2018 09:15, Jan Beulich wrote:
>> On 08.06.18 at 20:48, wrote:
@@ -3106,14 +3104,13 @@ static int vmx_msr_write_intercept(unsigned int
msr,
>> uint64_t msr_content)
for ( ; (rc ==
On 12/06/18 17:00, Manuel Bouyer wrote:
> On Tue, Jun 12, 2018 at 04:54:30PM +0100, Andrew Cooper wrote:
>> On 12/06/18 16:38, Manuel Bouyer wrote:
>>> On Tue, Jun 12, 2018 at 01:39:05PM +0200, Manuel Bouyer wrote:
I applied this patch to 4.11rc4 (let's not change too much things at the
s
On Tue, 12 Jun 2018, Julien Grall wrote:
> On a system where the firmware implements ARCH_WORKAROUND_2, it may be
> useful to either permanently enable or disable the workaround for cases
> where the user decides that they'd rather not get a trap overhead, and
> keep the mitigation permanently on o
On Tue, 12 Jun 2018, Julien Grall wrote:
> As for Spectre variant-2, we rely on SMCCC 1.1 to provide the discovery
> mechanism for detecting the SSBD mitigation.
>
> A new capability is also allocated for that purpose, and a config
> option.
>
> This is part of XSA-263.
>
> Signed-off-by: Julien
Hi,
On 12/06/18 16:55, Stefano Stabellini wrote:
On Tue, 12 Jun 2018, Julien Grall wrote:
Hi Stefano,
On 12/06/18 01:50, Stefano Stabellini wrote:
On Tue, 5 Jun 2018, Julien Grall wrote:
Hi Stefano,
On 04/06/18 18:24, Stefano Stabellini wrote:
Add a tiny kconfig configuration. Enabled NULL
On Tue, Jun 12, 2018 at 04:54:30PM +0100, Andrew Cooper wrote:
> On 12/06/18 16:38, Manuel Bouyer wrote:
> > On Tue, Jun 12, 2018 at 01:39:05PM +0200, Manuel Bouyer wrote:
> >> I applied this patch to 4.11rc4 (let's not change too much things at the
> >> same time) and rebooted my test host. Hopefu
On 08/06/18 12:12, Juergen Gross wrote:
> On 07/06/18 13:30, Juergen Gross wrote:
>> On 06/06/18 11:40, Juergen Gross wrote:
>>> On 06/06/18 11:35, Jan Beulich wrote:
>>> On 05.06.18 at 18:19, wrote:
>>> test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 14
>>> guest-saverestore.2
>>
On Tue, 12 Jun 2018, Julien Grall wrote:
> Hi Stefano,
>
> On 12/06/18 01:50, Stefano Stabellini wrote:
> > On Tue, 5 Jun 2018, Julien Grall wrote:
> > > Hi Stefano,
> > >
> > > On 04/06/18 18:24, Stefano Stabellini wrote:
> > > > Add a tiny kconfig configuration. Enabled NULL and Credit schedule
On 12/06/18 16:38, Manuel Bouyer wrote:
> On Tue, Jun 12, 2018 at 01:39:05PM +0200, Manuel Bouyer wrote:
>> I applied this patch to 4.11rc4 (let's not change too much things at the
>> same time) and rebooted my test host. Hopefully I'll have some data to report
>> soon
> Got the first panic (still
From: Oleksandr Grytsov
In the display protocol connector's id is named as unique-id. This patch renames
it in the libxl/xl code and uses XENDISPL_FIELD... definitions from the protocol
header.
Signed-off-by: Oleksandr Grytsov
---
docs/man/xl.cfg.pod.5.in| 2 +-
tools/libxl/libxl_types.id
From: Oleksandr Grytsov
As new version of the display protocol introduces unique-id variable, it needs
to be changed in libxl/xl. This patchset renames it in the xen store and in
display device structures. Also it uses XENDISPL_FIELD_... defines instead of
inline names.
Oleksandr Grytsov (1):
On Tue, Jun 12, 2018 at 01:39:05PM +0200, Manuel Bouyer wrote:
> I applied this patch to 4.11rc4 (let's not change too much things at the
> same time) and rebooted my test host. Hopefully I'll have some data to report
> soon
Got the first panic (still from a i386 domU):
login: (XEN) d4v0 Hit #DB i
On 06/12/2018 03:35 PM, Razvan Cojocaru wrote:
>>> @@ -210,7 +211,7 @@ static int p2m_init_altp2m(struct domain *d)
>>> return -ENOMEM;
>>> }
>>> p2m->p2m_class = p2m_alternate;
>>> -p2m->access_required = 1;
>>> +p2m->access_required = hostp2m->access
Am Tue, 12 Jun 2018 09:01:07 -0600
schrieb "Jan Beulich" :
> So there's no plan to fix this on the qemu side?
Even if there would be one, existing dom0s may not get an update in time.
I sent some prototype of a potential fix for qemu, it needs more work.
Olaf
pgpzDYSfvvGmr.pgp
Description: D
>>> On 12.06.18 at 16:10, wrote:
> Since qemu-2.10 it is required to unplug emulated devices again after
> a live migration. If this is not done, qemu's block-backend driver
> will be unable to open the backing disk image because it is still busy
> by qemu's IDE driver. As a result the domUs block
On Tue, Jun 12, 2018 at 04:16:53PM +0200, Jiri Denemark wrote:
> On Tue, Jun 12, 2018 at 07:57:40 -0500, Eric Blake wrote:
> > On 06/12/2018 06:11 AM, Jiri Denemark wrote:
> >
> > > I hit the same race twice on aarch64 and ppc64 and I can confirm the
> > > installation phase fails if libvirt.la is
flight 124108 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/124108/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
On Tue, Jun 12, 2018 at 07:57:40 -0500, Eric Blake wrote:
> On 06/12/2018 06:11 AM, Jiri Denemark wrote:
>
> > I hit the same race twice on aarch64 and ppc64 and I can confirm the
> > installation phase fails if libvirt.la is installed later than libraries
> > which link to it. However, the depend
Since qemu-2.10 it is required to unplug emulated devices again after
a live migration. If this is not done, qemu's block-backend driver
will be unable to open the backing disk image because it is still busy
by qemu's IDE driver. As a result the domUs block-frontend driver will
be unable to access
On 12/06/18 09:48, Oleksandr Andrushchenko wrote:
> From: Oleksandr Andrushchenko
>
> It is now only possible to control if multi-touch virtual device
> is created or not (via the corresponding XenStore entries),
> but keyboard and pointer devices are always created.
> In some cases this is not d
On 06/12/2018 04:46 PM, Juergen Gross wrote:
On 12/06/18 09:48, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
This is the sync up with the canonical definitions of the input,
sound and display protocols in Xen.
Changes to kbdif:
1. Add missing string constants for {feature|requ
When dom0-strict mode is enabled the iommu_inclusive_mapping workaround
for firmware with undeclared RMRRs is rendered useless. This series fixes
the problem.
Paul Durrant (2):
VT-d: re-phrase logic in vtd_set_hwdom_mapping() for clarity
VT-d: reconcile iommu_inclusive_mapping and iommu=dom0-s
The documentation for the iommu_inclusive_mapping Xen command line option
states:
"Use this to work around firmware issues providing incorrect RMRR entries"
Unfortunately this workaround does not function correctly if the dom0-strict
iommu option is also specified.
The documentation goes on to s
1 - 100 of 180 matches
Mail list logo
