gentle reminder
On 09/26/2017 02:35 PM, Oleksandr Andrushchenko wrote:
Clemens, Sakamoto-san,
could you please review the below if you by chance have a minute?
Thank you,
Oleksandr
On 09/19/2017 11:57 AM, Oleksandr Andrushchenko wrote:
Hi, all!
We did some work on implementing the idea with
>>> Yi Sun 09/29/17 4:58 AM >>>
>On 17-09-28 05:36:11, Jan Beulich wrote:
>> >>> On 23.09.17 at 11:48, wrote:
>> > This patch implements set value flow for MBA including its callback
>> > function and domctl interface.
>> >
>> > It also changes the memebers in 'cos_write_info' to transfer the
>>
flight 113991 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113991/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 113972
build-armhf
>>> Yi Sun 09/29/17 3:55 AM >>>
>On 17-09-28 05:00:09, Jan Beulich wrote:
>> >>> On 23.09.17 at 11:48, wrote:
>> > One thrtl register of MBA stores a throttle value for one or more
>> > domains. The throttle value means the delay between L2 cache and next
>> > cache level.
>>
>> What is a delay
>>> Yi Sun 09/29/17 3:37 AM >>>
>On 17-09-28 04:21:10, Jan Beulich wrote:
>> >>> On 23.09.17 at 11:48, wrote:
>> > --- a/xen/include/public/domctl.h
>> > +++ b/xen/include/public/domctl.h
>> > @@ -37,7 +37,7 @@
>> > #include "hvm/save.h"
>> > #include "memory.h"
>> >
>> > -#define XEN_DOMCTL_
>>> Dario Faggioli 09/28/17 7:17 PM >>>
>On Thu, 2017-09-28 at 07:06 -0600, Jan Beulich wrote:
>> > > > On 28.09.17 at 12:16, wrote:
>> >
>> And then, as a cosmetic thing, idle_timer_period_ms now isn't
>> really needed outside of this function. I'd prefer if you moved it
>> and the integer_para
>>> Julien Grall 09/28/17 9:30 PM >>>
>On 09/22/2017 10:15 AM, Jan Beulich wrote:
> On 21.09.17 at 14:40, wrote:
>>> Also take the opportunity to:
>>> - move from 1 << * to 1UL << *.
>>> - use unsigned when possible
>>> - move from unsigned int -> unsigned long for some inducti
Hi
On 10/3/2017 8:01 PM, Julien Grall wrote:
Hi,
On 21/09/17 14:17, mja...@caviumnetworks.com wrote:
From: Manish Jaggi
estimate_acpi_efi_size needs to be updated to provide correct size of
hardware domains MADT, which now adds ITS information as well.
Introducing gic_get_hwdom_madt_size.
Hello Julien,
On 10/3/2017 7:17 PM, Julien Grall wrote:
Hi Manish,
On 21/09/17 14:17, mja...@caviumnetworks.com wrote:
From: Manish Jaggi
Added gicv3_its_acpi_init to update host_its_list from MADT table.
For ACPI, host_its structure stores dt_node as NULL.
Signed-off-by: Manish Jaggi
---
Hello Julien,
On 10/4/2017 12:12 AM, Julien Grall wrote:
Hello,
On 25/09/17 05:22, Manish Jaggi wrote:
On 9/22/2017 7:42 PM, Andre Przywara wrote:
Hi Manish,
On 11/09/17 22:33, mja...@caviumnetworks.com wrote:
From: Manish Jaggi
The set is divided into two patches. First one calculates th
flight 113974 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113974/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 saverestore-support-checkfail like 113876
test-amd64-i386-xl-qemuu-win7-amd64
flight 113989 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113989/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 113972
build-armhf
This run is configured for baseline tests only.
flight 72194 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/72194/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf fe4049471bdf066c3c07dfa76752149743afa16f
baseline v
flight 113986 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113986/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 113972
build-armhf
This run is configured for baseline tests only.
flight 72193 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/72193/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-pair 10 xen-boot/src_h
flight 113979 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113979/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 113972
build-armhf
flight 113970 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113970/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-amd64 15 guest-saverestore.2 fail REGR.
vs. 113945
test-amd64
flight 113972 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113972/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-armhf-armhf-xl 1
Le mardi 03 octobre 2017 à 11:22 +0200, Dario Faggioli a écrit :
> What's the version of your guest kernel?
4.9.52, so yes, it seems to be that, I will try to patch and follow
this issue.
Thanks !
Olivier
___
Xen-devel mailing list
Xen-devel@lists.xen
On Fri, 29 Sep 2017, Stefano Stabellini wrote:
> On Fri, 29 Sep 2017, Julien Grall wrote:
> > Hi Stefano,
> >
> > On 09/29/2017 09:10 PM, Stefano Stabellini wrote:
> > > On Wed, 27 Sep 2017, Bhupinder Thakur wrote:
> > > > DEFINE_XEN_FLEX_RING(xencons) defines common helper functions such as
> > >
On 10/03/2017 11:20 AM, Sergey Dyasli wrote:
> Remove np2m_base parameter as it should always match the value of
> np2m_base in VMCx12.
>
> Signed-off-by: Sergey Dyasli
> Reviewed-by: George Dunlap
SVM bits:
Reviewed-by: Boris Ostrovsky
___
Xen-de
On 10/02/2017 05:37 PM, HW42 wrote:
> Juergen Gross:
>> When setting up the Xenstore watch for the memory target size the new
>> watch will fire at once. Don't try to reach the configured target size
>> by onlining new memory in this case, as the current memory size will
>> be smaller in almost all
flight 113964 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113964/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-amd64 16 guest-localmigrate/x10 fail REGR.
vs. 113876
test-
flight 113971 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113971/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-i386 16 guest-localmigrate/x10 fail REGR.
vs. 113952
T
flight 113967 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113967/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf fe4049471bdf066c3c07dfa76752149743afa16f
baseline version:
ovmf 9425b34925d0cf1b96aaf
Bringing this commit into xen.git needs coordination with the
corresponding change to introduce the new library: this commit nees to
be introdeuced to xen.git immediately after
xentoolcore, _restrict_all: Introduce new library and implementation
Signed-off-by: Ian Jackson
---
Makefile | 2 ++
Hello,
On 25/09/17 05:22, Manish Jaggi wrote:
On 9/22/2017 7:42 PM, Andre Przywara wrote:
Hi Manish,
On 11/09/17 22:33, mja...@caviumnetworks.com wrote:
From: Manish Jaggi
The set is divided into two patches. First one calculates the size of
IORT
while second one writes the IORT table its
This hook appears to be missing from the Linux ubsan implemention. This patch
is a forward port of https://lkml.org/lkml/2014/10/20/182
Signed-off-by: Andrew Cooper
---
CC: George Dunlap
CC: Jan Beulich
CC: Konrad Rzeszutek Wilk
CC: Stefano Stabellini
CC: Tim Deegan
CC: Wei Liu
CC: Julien
A future change will adjust it to compile in Xen.
Signed-off-by: Andrew Cooper
Signed-off-by: Wei Liu
---
CC: George Dunlap
CC: Jan Beulich
CC: Konrad Rzeszutek Wilk
CC: Stefano Stabellini
CC: Tim Deegan
CC: Wei Liu
CC: Julien Grall
---
xen/common/ubsan/Makefile | 1 +
xen/common/ubsan
Andrew Cooper (4):
xen/tmem: Drop unnecessary noinline attribute
xen/ubsan: Import ubsan implementation from Linux 4.13
xen/ubsan: Implement __ubsan_handle_nonnull_arg()
xen/ubsan: Introduce and use CONFIG_UBSAN
xen/Kconfig| 6 +
xen/Kconfig.debug | 8 +
xen/R
tmem_mempool_page_get() is only referenced by address, so isn't eligable for
inlining in the first place.
Signed-off-by: Andrew Cooper
---
CC: Konrad Rzeszutek Wilk
Not related to the rest of the series, but I stumbled across it while
resolving another noinline issue.
---
xen/common/tmem.c | 2
Tested with GCC 4.9 of Debian Jessie.
Signed-off-by: Andrew Cooper
Signed-off-by: Wei Liu
---
CC: George Dunlap
CC: Jan Beulich
CC: Konrad Rzeszutek Wilk
CC: Stefano Stabellini
CC: Tim Deegan
CC: Wei Liu
CC: Julien Grall
TODO at some future point: Fix the following known issues:
Clang
Adds 3 messages to allow guest to let backend keep grants mapped,
such that 1) guests allowing fast recycling of pages can avoid doing
grant ops for those cases, or otherwise 2) preferring copies over
grants and 3) always using a fixed set of pages for network I/O.
The three control ring messages
Hey,
This is v5 from netif series. The new thing (besides the tags being added) is
the specification (previously written in the cover letter) being added to docs
as requested by Konrad. And all seems to be RoB.
Reference implementation also here (on top of net-next):
https://github.com/jpemartin
Add a document outlining how the guest can map a set of grants
on the backend through the control ring.
Signed-off-by: Joao Martins
Reviewed-by: Konrad Rzeszutek Wilk
---
New in v5
---
docs/misc/netif-staging-grants.pandoc | 587 ++
1 file changed, 587 insertions
On Mon, 2 Oct 2017, Eduardo Habkost wrote:
> On Thu, Sep 28, 2017 at 10:12:34AM -0300, Eduardo Habkost wrote:
> > On Thu, Sep 28, 2017 at 02:33:57AM -0600, Jan Beulich wrote:
> > > >>> On 27.09.17 at 21:56, wrote:
> > > > --- a/hw/xen/xen_pt.c
> > > > +++ b/hw/xen/xen_pt.c
> > > > @@ -964,6 +964,1
flight 113962 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113962/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-libvirt-xsm 21 leak-check/check fail in 113959 pass in 113962
test-armhf-armhf-xl-multivcpu 5
On Tue, Oct 03, 2017 at 03:48:56PM +0100, Andrew Cooper wrote:
> 0xf << 12 is undefined behaviour, due to shifting into the sign bit of an
> integer.
>
> Spotted by the Undefined Behaviour Sanitiser
>
> Signed-off-by: Andrew Cooper
Reviewed-by: Wei Liu
Hi,
On 03/10/17 17:19, Andrew Cooper wrote:
On 03/10/17 17:03, Wei Liu wrote:
diff --git a/xen/common/ubsan/ubsan.c b/xen/common/ubsan/ubsan.c
new file mode 100644
index 00..aa359e712c
--- /dev/null
+++ b/xen/common/ubsan/ubsan.c
@@ -0,0 +1,486 @@
+/*
+ * UBSAN error reporting functions
On Tue, Oct 03, 2017 at 05:19:44PM +0100, Andrew Cooper wrote:
> On 03/10/17 17:03, Wei Liu wrote:
> > 1. Introduce Kconfig UBSAN option.
> > 2. Import and adapt a bunch of hooks from Linux kernel with as little
> >modification as possible.
> > 3. Provide mechanism to filter out unwanted files.
Hi Wei,
On 03/10/17 17:03, Wei Liu wrote:
1. Introduce Kconfig UBSAN option.
2. Import and adapt a bunch of hooks from Linux kernel with as little
modification as possible.
3. Provide mechanism to filter out unwanted files.
This is x86 only at the moment. It should be easy to make it work o
On 03/10/17 17:03, Wei Liu wrote:
> 1. Introduce Kconfig UBSAN option.
> 2. Import and adapt a bunch of hooks from Linux kernel with as little
>modification as possible.
> 3. Provide mechanism to filter out unwanted files.
>
> This is x86 only at the moment. It should be easy to make it work on
1. Introduce Kconfig UBSAN option.
2. Import and adapt a bunch of hooks from Linux kernel with as little
modification as possible.
3. Provide mechanism to filter out unwanted files.
This is x86 only at the moment. It should be easy to make it work on
arm, but I don't have the test environment t
Remove some code duplication.
Suggested-by: George Dunlap
Signed-off-by: Sergey Dyasli
Reviewed-by: George Dunlap
---
xen/arch/x86/mm/p2m.c | 25 ++---
1 file changed, 10 insertions(+), 15 deletions(-)
diff --git a/xen/arch/x86/mm/p2m.c b/xen/arch/x86/mm/p2m.c
index 90bf38
At the moment, nested p2ms are not shared between vcpus even if they
share the same base pointer.
Modify p2m_get_nestedp2m() to allow sharing a np2m between multiple
vcpus with the same np2m_base (L1 np2m_base value in VMCx12).
If the current np2m doesn't match the current base pointer, first loo
Flush IPIs are sent to all cpus in an np2m's dirty_cpumask when
updated. This mask however is far too broad. A pcpu's bit is set in
the cpumask when a vcpu runs on that pcpu, but is only cleared when a
flush happens. This means that the IPI includes the current pcpu of
vcpus that are not current
Remove np2m_base parameter as it should always match the value of
np2m_base in VMCx12.
Signed-off-by: Sergey Dyasli
Reviewed-by: George Dunlap
---
xen/arch/x86/hvm/svm/nestedsvm.c | 6 +-
xen/arch/x86/hvm/vmx/vvmx.c | 3 +--
xen/arch/x86/mm/hap/nested_hap.c | 2 +-
xen/arch/x86/mm/p2m.
Nested p2m (shadow EPT) is an object that stores memory address
translations from L2 GPA directly to L0 HPA. This is achieved by
combining together L1 EPT with L0 EPT during L2 EPT violations.
In the usual case, L1 uses the same EPTP value in VMCS12 for all vCPUs
of a L2 guest. But unfortunately,
At the moment, the shadow EPTP value is written unconditionally in
ept_handle_violation().
Instead, write the value on vmentry to the guest; but only write it if
the value needs updating.
To detect this, add a flag to the nestedvcpu struct, stale_np2m, to
indicate when such an action is necessary
1. Add a helper function assign_np2m()
2. Remove useless volatile
3. Update function's comment in the header
4. Minor style fixes ('\n' and d)
Signed-off-by: Sergey Dyasli
Reviewed-by: George Dunlap
---
xen/arch/x86/mm/p2m.c | 31 ++-
xen/include/asm-x86/p2m.h |
Now that np2m sharing is implemented, there can be only one np2m object
with the same np2m_base. Break from loop if the required np2m was found
during np2m_flush_eptp().
Signed-off-by: Sergey Dyasli
Reviewed-by: George Dunlap
---
xen/arch/x86/mm/p2m.c | 4
xen/include/asm-x86/p2m.h | 2
At the moment, nvmx_handle_invept() updates the current np2m just to
flush it. Instead introduce a function, np2m_flush_base(), which will
look up the np2m base pointer and call p2m_flush_table() instead.
Unfortunately, since we don't know which p2m a given vcpu is using, we
must flush all p2ms t
On Tue, Oct 03, 2017 at 02:12:22PM +, Andrew Cooper wrote:
> On 03/10/17 15:04, Roger Pau Monné wrote:
> > On Fri, Sep 29, 2017 at 06:31:03PM +, Andrew Cooper wrote:
> >> This rearanges the logic to avoid the double !hvm_paging_enabled(v) check,
> >> but
> >> is otherwise identical.
> >>
>
There is a possibility for nested_p2m to became stale between
nestedhvm_hap_nested_page_fault() and nestedhap_fix_p2m(). At the moment
this is handled by detecting such a race inside nestedhap_fix_p2m() and
special-casing it.
Instead, introduce p2m_get_nestedp2m_locked(), which will returned a
st
0xf << 12 is undefined behaviour, due to shifting into the sign bit of an
integer.
Spotted by the Undefined Behaviour Sanitiser
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Wei Liu
I appear to have missed this patch from my past UBSAN work.
---
xen/include/asm-x86/msr-index.h | 2
Hi Manish,
On 21/09/17 14:17, mja...@caviumnetworks.com wrote:
From: Manish Jaggi
Add gicv3_its_make_hwdom_madt to update hwdom MADT ITS information.
Signed-off-by: Manish Jaggi
---
xen/arch/arm/gic-v3-its.c| 19 +++
xen/arch/arm/gic-v3.c| 1 +
xen/in
Hi,
On 21/09/17 14:17, mja...@caviumnetworks.com wrote:
From: Manish Jaggi
estimate_acpi_efi_size needs to be updated to provide correct size of
hardware domains MADT, which now adds ITS information as well.
Introducing gic_get_hwdom_madt_size.
I think the commit title is misleading, the ma
Hi Manish,
On 21/09/17 14:17, mja...@caviumnetworks.com wrote:
From: Manish Jaggi
This patch extends the gicv3_iomem_deny_access functionality by adding
support for ITS region as well. Add function gicv3_its_deny_access.
Signed-off-by: Manish Jaggi
Acked-by: Julien Grall
Cheers,
--
Juli
flight 72186 distros-debian-snapshot real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/72186/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-armhf-daily-netboot-pygrub 1 build-check(1) blocked n/a
build-arm64-pvops
On 03/10/17 15:04, Roger Pau Monné wrote:
> On Fri, Sep 29, 2017 at 06:31:03PM +, Andrew Cooper wrote:
>> This rearanges the logic to avoid the double !hvm_paging_enabled(v) check,
>> but
>> is otherwise identical.
>>
>> Signed-off-by: Andrew Cooper
>> ---
>> CC: Jan Beulich
>> CC: Jun Nakaj
On Fri, Sep 29, 2017 at 06:31:03PM +, Andrew Cooper wrote:
> This rearanges the logic to avoid the double !hvm_paging_enabled(v) check, but
> is otherwise identical.
>
> Signed-off-by: Andrew Cooper
> ---
> CC: Jan Beulich
> CC: Jun Nakajima
> CC: Kevin Tian
> ---
> xen/arch/x86/hvm/vmx/v
Hi Manish,
On 21/09/17 14:17, mja...@caviumnetworks.com wrote:
From: Manish Jaggi
Added gicv3_its_acpi_init to update host_its_list from MADT table.
For ACPI, host_its structure stores dt_node as NULL.
Signed-off-by: Manish Jaggi
---
xen/arch/arm/gic-v3-its.c| 24 +
Le vendredi 29 septembre 2017 à 10:20 +0100, Roger Pau Monné a écrit :
> On Thu, Sep 28, 2017 at 05:27:54PM +, Olivier Bonvalet wrote:
> > Le jeudi 28 septembre 2017 à 17:12 +0100, Roger Pau Monné a écrit :
> > >
> > > Quite likely. With so many PV block devices attached you either
> > > have
Paolo Bonzini wrote:
> On 02/10/2017 12:36, George Dunlap wrote:
Although I'm not business man, I don't think the top cloud provider[s]
would allow nested virtualization, however mature nested virtualization
is. Even xen-pv is unable to be nested in the aws and azure.
>>>
>>> Chec
Hi Juergen,
On 28/09/17 11:02, Juergen Gross wrote:
Instead of using the same global resource limits of grant tables (max.
number of grant frames, max. number of maptrack frames) for all domains
make these limits per domain. Set those per-domain limits in
grant_table_set_limits(). The global set
Hi Volodymyr,
On 21/09/17 21:00, Volodymyr Babchuk wrote:
diff --git a/xen/arch/arm/psci.c b/xen/arch/arm/psci.c
index 34ee97e..be4e8e6 100644
--- a/xen/arch/arm/psci.c
+++ b/xen/arch/arm/psci.c
@@ -31,9 +31,9 @@
* (native-width) function ID.
*/
#ifdef CONFIG_ARM_64
-#define PSCI_0_2_FN_
Hi Volodymyr,
On 21/09/17 21:00, Volodymyr Babchuk wrote:
PSCI is part of HVC/SMC interface, so it should be handled in
appropriate place: `vsmc.c`. This patch moves PSCI handler
calls from `traps.c` to `vsmc.c`. Also it corrects coding
style of the PSCI handler functions.
Older PSCI 0.1 uses S
On 10/03/2017 07:55 AM, Joao Martins wrote:
In order to support pvclock vdso on xen we need to setup the time
info page for vcpu 0 and register the page with Xen using the
VCPUOP_register_vcpu_time_memory_area hypercall. This hypercall
will also forcefully update the pvti which will set some of
On 10/03/2017 04:56 AM, Roger Pau Monné wrote:
On Fri, Sep 29, 2017 at 05:22:25PM +, Boris Ostrovsky wrote:
On 09/29/2017 01:07 PM, Roger Pau Monné wrote:
On Fri, Sep 29, 2017 at 05:02:48PM +, Boris Ostrovsky wrote:
On 09/29/2017 11:51 AM, Roger Pau Monné wrote:
On Fri, Sep 29, 2017
Hi Volodymyr,
On 21/09/17 21:00, Volodymyr Babchuk wrote:
SMCCC (SMC Call Convention) describes how to handle both HVCs and SMCs.
SMCCC states that both HVC and SMC are valid conduits to call to different
firmware functions. Thus, for example, PSCI calls can be made both by
SMC or HVC. Also SMCC
Hi Volodymyr,
On 21/09/17 20:59, Volodymyr Babchuk wrote:
Add generic definitions used in ARM SMC call convention.
Those definitions was originaly added to Linux kernel as
s/originaly/originally/
include/linux/arm-smccc.h by commit 98dd64f34f47
("ARM: 8478/2: arm/arm64: add arm-smccc")
I ex
Roger Pau Monne writes ("[PATCH v2 3/3] osstest: limit PVH tests to Xen >=
4.10"):
> Older Xen versions don't support the 'type' xl option used to create a
> PVHv2 guest.
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https:/
Roger Pau Monne writes ("[PATCH v2 1/3] osstest: fix PVH DomU tests"):
> The pvh=1 xl option was removed, so switch the PVH tests to use
> type='pvh' instead.
>
> On older branches still supporting PVHv1 (and the 'pvh' xl option),
> this change will turn the PVH tests into PV tests). A followup ch
Hi,
On 21/09/17 20:59, Volodymyr Babchuk wrote:
Added type xen_uuid_t. This type represents UUID as an array of 16
bytes in big endian format.
Added macro XEN_DEFINE_UUID that constructs UUID in the usual way:
XEN_DEFINE_UUID(0x00112233, 0x4455, 0x6677, 0x8899, 0xaabbccddeeff)
will construc
On Fri, Sep 29, 2017 at 06:31:02PM +, Andrew Cooper wrote:
> An update to CR4 following a CR0 update can be done easily by falling
> through into the CR4 case. This avoids unnecessary passes through
> vmx_vmcs_{enter,exit}() and unnecessary stack usage (as the compiler
> cannot optimise this u
Specifically check for PVCLOCK_TSC_STABLE_BIT and if this bit is set,
then set it too on pvclock flags. This allows Xen clocksource to use it
and thus speeding up xen_clocksource_read() callers (i.e. sched_clock())
Signed-off-by: Joao Martins
Reviewed-by: Boris Ostrovsky
---
Changes since v5:
*
In order to support pvclock vdso on xen we need to setup the time
info page for vcpu 0 and register the page with Xen using the
VCPUOP_register_vcpu_time_memory_area hypercall. This hypercall
will also forcefully update the pvti which will set some of the
necessary flags for vdso. Afterwards we che
Right now there is only a pvclock_pvti_cpu0_va() which is defined
on kvmclock since:
commit dac16fba6fc5
("x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap")
The only user of this interface so far is kvm. This commit adds a
setter function for the pvti page and moves pvclock_pvt
Hey,
This is take 6 for vdso for Xen. PVCLOCK_TSC_STABLE_BIT can be set starting Xen
4.8 which is required for vdso time related calls. In order to have it on, you
need to have the hypervisor clocksource be TSC e.g. with the following boot
params "clocksource=tsc tsc=stable:socket".
Series is st
This file defines an ABI shared between guest and hypervisor(s)
(KVM, Xen) and as such there should be an correspondent entry in
MAINTAINERS file. Notice that there's already a text notice at the
top of the header file, hence this commit simply enforces it more
explicitly and have both peers notice
On Fri, Sep 29, 2017 at 06:31:01PM +, Andrew Cooper wrote:
> * Drop trailing whitespace
> * Fix indendation and newlines
> * Use bool where appropriate
>
> No functional change.
>
> Signed-off-by: Andrew Cooper
Reviewed-by: Roger Pau Monné
Thanks, Roger.
__
On Tue, Oct 03, 2017 at 12:33:37PM +0100, Roger Pau Monné wrote:
> On Mon, Oct 02, 2017 at 04:30:58PM +, Anthony PERARD wrote:
> > When doing a live migration of a Xen guest with libxl, the images for
> > block devices are locked by the original QEMU process, and this prevent
> > the QEMU at th
On 28/09/17 23:49, Andre Przywara wrote:
Hi,
Hi,
On 09/28/2017 01:03 PM, Julien Grall wrote:
#define SUNXI_WDT_MODE0x04
-#define SUNXI_WDT_MODEADDR(SUNXI_WDT_BASE + SUNXI_WDT_MODE)
#define SUNXI_WDT_MODE_EN (1 << 0)
#define SUNXI_WDT_MODE_RST_EN (1 <<
On Mon, Oct 02, 2017 at 04:30:58PM +, Anthony PERARD wrote:
> When doing a live migration of a Xen guest with libxl, the images for
> block devices are locked by the original QEMU process, and this prevent
> the QEMU at the destination to take the lock and the migration fail.
>
> From QEMU poi
This run is configured for baseline tests only.
flight 72185 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/72185/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-examine 10 examine-serial/
Hi,
On 29/09/17 10:03, George Dunlap wrote:
On 09/28/2017 07:36 PM, Andrew Cooper wrote:
... instead of the opencoded _mfn(pagetable_get_pfn(...)) construct.
Fix two overly long lines; no functional change.
Signed-off-by: Andrew Cooper
Reviewed-by: George Dunlap
I think this technically
The previous builder='hvm' is also kept for compatibility with older
Xen releases. Note that the type option is ignored in previous Xen
versions.
Signed-off-by: Roger Pau Monné
Acked-by: Ian Jackson
---
Cc: ian.jack...@eu.citrix.com
---
Osstest/TestSupport.pm | 1 +
1 file changed, 1 insertion(
Older Xen versions don't support the 'type' xl option used to create a
PVHv2 guest.
Signed-off-by: Roger Pau Monné
---
Cc: Ian Jackson
---
Changes since v1:
- New in this version.
---
make-flight | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/make-flight b/make-fli
Hello,
The patches in this series modify osstest in order to fix the PVH
tests, switch HVM guests to use the 'type' option (note that
the builder option is kept for compatibility reasons) and remove the PVH
tests from branches older than Xen 4.10.
Thanks, Roger.
Roger Pau Monne (3):
osstest: f
The pvh=1 xl option was removed, so switch the PVH tests to use
type='pvh' instead.
On older branches still supporting PVHv1 (and the 'pvh' xl option),
this change will turn the PVH tests into PV tests). A followup change
will remove the PVH tests from those branches, since PVHv1 has already
been
On Tue, Oct 03, 2017 at 09:55:44AM +, osstest service owner wrote:
> flight 113959 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/113959/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-
flight 113959 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113959/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-xsm 21 leak-check/check fail REGR. vs. 113954
test-armhf-armhf-x
On Fri, Sep 29, 2017 at 05:19:52PM +, Ian Jackson wrote:
> Roger Pau Monné writes ("Re: [PATCH 1/2] osstest: fix PVH DomU tests"):
> > On Fri, Sep 29, 2017 at 03:35:24PM +, Ian Jackson wrote:
> > > I think it might stop the pvh tests from working in those branches.
> >
> > This change will
On Mon, 2017-10-02 at 18:37 +0200, Olivier Bonvalet wrote:
> root! laussor:/proc# cat /proc/uptime
> 652005.23 2631328.82
>
>
> Values for "stolen time" in /proc/stat seems impossible with only 7
> days of uptime.
>
I think it can be this:
https://0xstubs.org/debugging-a-flaky-cpu-steal-time-co
On Mon, Oct 02, 2017 at 04:32:39PM +, Olivier Bonvalet wrote:
> Le vendredi 29 septembre 2017 à 10:20 +0100, Roger Pau Monné a écrit :
> > On Thu, Sep 28, 2017 at 05:27:54PM +, Olivier Bonvalet wrote:
> > > Le jeudi 28 septembre 2017 à 17:12 +0100, Roger Pau Monné a écrit :
> > > >
> > > >
On Fri, Sep 29, 2017 at 05:22:25PM +, Boris Ostrovsky wrote:
> On 09/29/2017 01:07 PM, Roger Pau Monné wrote:
> > On Fri, Sep 29, 2017 at 05:02:48PM +, Boris Ostrovsky wrote:
> >> On 09/29/2017 11:51 AM, Roger Pau Monné wrote:
> >>> On Fri, Sep 29, 2017 at 03:33:58PM +, Juergen Gross wr
flight 113960 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/113960/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 saverestore-support-checkfail like 113898
test-armhf-armhf-libvirt-xsm 14 saveresto
On Fri, Sep 29, 2017 at 11:12 PM, Julien Grall wrote:
>
>
> On 09/29/2017 09:15 AM, bharat gohil wrote:
>
>> Hello
>>
>
> Hi,
>
> Please avoid top-posting.
>
> The patch didn't work in my case.
>>
>
> The patch will be useful only if the compatible string in the DT of your
> UART is "snps,dw-apb-
98 matches
Mail list logo