[Xen-devel] [qemu-mainline test] 115456: regressions - FAIL

flight 115456 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/115456/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i3866 xen-buildfail REGR. vs. 114507 build-amd64-xsm

[Xen-devel] [linux-linus test] 115438: regressions - FAIL

flight 115438 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/115438/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail REGR. vs. 114682 Tests which are fai

Re: [Xen-devel] [RFC] ARM: New (Xen) VGIC design document

On Wed, Nov 1, 2017 at 9:58 AM, Stefano Stabellini wrote: [] > >> ### List register management >> >> A list register (LR) holds the state of a virtual interrupt, which will >> be used by the GIC hardware to simulate an IRQ life cycle for a guest. >> Each GIC hardware implementation can choos

[Xen-devel] [qemu-mainline bisection] complete build-armhf

branch xen-unstable xenbranch xen-unstable job build-armhf testid xen-build Tree: qemuu git://git.qemu.org/qemu.git Tree: xen git://xenbits.xen.org/xen.git *** Found and reproduced problem changeset *** Bug is in tree: qemuu git://git.qemu.org/qemu.git Bug introduced: aef45d51d1204f3335fb9

[Xen-devel] [linux-4.9 test] 115432: regressions - FAIL

flight 115432 linux-4.9 real [real] http://logs.test-lab.xenproject.org/osstest/logs/115432/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail REGR. vs. 114814 Tests which are faili

Re: [Xen-devel] [PATCH] aarch64: advertise the GIC system register interface

On Tue, 31 Oct 2017, Peter Maydell wrote: > On 31 October 2017 at 18:51, Stefano Stabellini > wrote: > > On Tue, 31 Oct 2017, Peter Maydell wrote: > >> On 31 October 2017 at 17:01, Stefano Stabellini > >> wrote: > >> > Fixing QEMU is harder than I expected. Would it be possible to update > >> >

[Xen-devel] [qemu-mainline test] 115452: regressions - FAIL

flight 115452 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/115452/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i3866 xen-buildfail REGR. vs. 114507 build-amd64-xsm

Re: [Xen-devel] [RFC] ARM: New (Xen) VGIC design document

On Wed, 11 Oct 2017, Andre Przywara wrote: > Hi, > > (CC:ing some KVM/ARM folks involved in the VGIC) > > starting with the addition of the ITS support we were seeing more and > more issues with the current implementation of our ARM Generic Interrupt > Controller (GIC) emulation, the VGIC. > Amon

[Xen-devel] [PATCH v6 1/1] xen/time: do not decrease steal time after live migration on xen

After guest live migration on xen, steal time in /proc/stat (cpustat[CPUTIME_STEAL]) might decrease because steal returned by xen_steal_lock() might be less than this_rq()->prev_steal_time which is derived from previous return value of xen_steal_clock(). For instance, steal time of each vcpu is 33

Re: [Xen-devel] [PATCH 3/3] x86/svm: add virtual VMLOAD/VMSAVE support

On Tue, Oct 31, 2017 at 10:15:08PM +, Andrew Cooper wrote: > > The style in this file is quite hit and miss, but we expect new code to > conform to the standards.  In this case, the correct style is: > > if ( cpu_has_svm_vloadsave ) > { > > This can be fixed on commit if there are no other c

Re: [Xen-devel] [PATCH 3/3] x86/svm: add virtual VMLOAD/VMSAVE support

On 31/10/17 22:03, brian.wo...@amd.com wrote: > From: Brian Woods > > On AMD family 17h server processors, there is a feature called virtual > VMLOAD/VMSAVE. This allows a nested hypervisor to preform a VMLOAD or > VMSAVE without needing to be intercepted by the host hypervisor. > Virtual VMLOAD/

[Xen-devel] [PATCH 2/3] x86/svm: add virtual VMLOAD/VMSAVE feature definition

From: Brian Woods Adding support for enabling the virtual VMLOAD/VMSAVE feature.. Signed-off-by: Brian Woods --- xen/include/asm-x86/hvm/svm/svm.h | 2 ++ xen/include/asm-x86/hvm/svm/vmcb.h | 1 + 2 files changed, 3 insertions(+) diff --git a/xen/include/asm-x86/hvm/svm/svm.h b/xen/include/

[Xen-devel] [PATCH 1/3] x86/svm: rename lbr control field in vmcb

From: Brian Woods Rename the lbr_control field in the vmcb for future/upcoming changes. Signed-off-by: Brian Woods --- xen/arch/x86/hvm/svm/nestedsvm.c| 10 +- xen/arch/x86/hvm/svm/svm.c | 2 +- xen/include/asm-x86/hvm/svm/nestedsvm.h | 4 ++-- xen/include/asm-x8

[Xen-devel] [PATCH 0/3] x86/svm: virtual VMLOAD/VMSAVE

From: Brian Woods x86/svm: virtual VMLOAD/VMSAVE On AMD family 17h server processors, there is a feature called virtual VMLOAD/VMSAVE. This allows a nested hypervisor to preform a VMLOAD or VMSAVE without needing to be intercepted by the host hypervisor. Virtual VMLOAD/VMSAVE requires the host

[Xen-devel] [PATCH 3/3] x86/svm: add virtual VMLOAD/VMSAVE support

From: Brian Woods On AMD family 17h server processors, there is a feature called virtual VMLOAD/VMSAVE. This allows a nested hypervisor to preform a VMLOAD or VMSAVE without needing to be intercepted by the host hypervisor. Virtual VMLOAD/VMSAVE requires the host hypervisor to be in long mode an

[Xen-devel] [qemu-mainline test] 115444: regressions - FAIL

flight 115444 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/115444/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i3866 xen-buildfail REGR. vs. 114507 build-amd64-xsm

Re: [Xen-devel] [PATCH] gdbsx: prefer privcmd character device

On Tue, Oct 31, 2017 at 03:25:39PM +, Wei Liu wrote: > On Tue, Oct 31, 2017 at 10:20:11AM -0500, Doug Goldstein wrote: > > Prefer using the character device over the proc file if the character > > device exists. > > > > CC: Elena Ufimtseva > > CC: Ian Jackson > > CC: Stefano Stabellini > >

[Xen-devel] [xen-unstable test] 115419: regressions - FAIL

flight 115419 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/115419/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stopfail REGR. vs. 114644 test-amd64-amd64-x

Re: [Xen-devel] [PATCH] aarch64: advertise the GIC system register interface

On 31 October 2017 at 18:51, Stefano Stabellini wrote: > On Tue, 31 Oct 2017, Peter Maydell wrote: >> On 31 October 2017 at 17:01, Stefano Stabellini >> wrote: >> > Fixing QEMU is harder than I expected. Would it be possible to update >> > id_aa64pfr0 at CPU reset time? Like cpu->id_aa64pfr0 |=

[Xen-devel] [PATCH RFC for-next] x86/mm: introduce and use virt_to_xen_l4e

Avoid open-coding in a lot of places. No functional change. Signed-off-by: Wei Liu --- Is this patch useful or is open-coding preferred? --- xen/arch/x86/mm.c | 14 +++--- xen/arch/x86/x86_64/mm.c | 36 +--- xen/include/asm-x86/page.h | 5

Re: [Xen-devel] [PATCH] aarch64: advertise the GIC system register interface

On Tue, 31 Oct 2017, Peter Maydell wrote: > On 31 October 2017 at 17:01, Stefano Stabellini > wrote: > > Fixing QEMU is harder than I expected. Would it be possible to update > > id_aa64pfr0 at CPU reset time? Like cpu->id_aa64pfr0 |= 0x0100; ? > > At that point we've already called register

Re: [Xen-devel] [OSSTEST PATCH v2 00/19] Upgrade to Stretch

On Tue, Oct 31, 2017 at 01:51:44PM +, Wei Liu wrote: > First version of this series can be found at [0]. > > This version contains workaround for Arndale boards. They are now functional. > > A bunch of test cases failed: > > 1. Rumpkernel tests -- I've sent an email to Antti for advice. > 2.

Re: [Xen-devel] [PATCH v2] xen: support 52 bit physical addresses in pv guests

On 10/27/2017 01:49 PM, Juergen Gross wrote: > Physical addresses on processors supporting 5 level paging can be up to > 52 bits wide. For a Xen pv guest running on such a machine those > physical addresses have to be supported in order to be able to use any > memory on the machine even if the gues

Re: [Xen-devel] [PATCH v8 00/13] introduce the Xen PV Calls frontend

On 10/30/2017 06:40 PM, Stefano Stabellini wrote: > Hi all, > > this series introduces the frontend for the newly introduced PV Calls > procotol. > > PV Calls is a paravirtualized protocol that allows the implementation of > a set of POSIX functions in a different domain. The PV Calls frontend > se

Re: [Xen-devel] [PATCH for-4.10] common/multicall: Increase debugability for bad hypercalls

On Tue, Oct 31, 2017 at 05:18:52PM +, Andrew Cooper wrote: > While investigating an issue (in a new codepath I'd introduced, as it turns > out), leaving interrupts disabled manifested as a subsequent op in the > multicall failing a check_lock() test. > > The codepath would have hit the ASSERT_

Re: [Xen-devel] [PATCH for-4.10] common/multicall: Increase debugability for bad hypercalls

On 10/31/2017 05:18 PM, Andrew Cooper wrote: > While investigating an issue (in a new codepath I'd introduced, as it turns > out), leaving interrupts disabled manifested as a subsequent op in the > multicall failing a check_lock() test. > > The codepath would have hit the ASSERT_NOT_IN_ATOMIC on t

[Xen-devel] [PATCH for-4.10] common/multicall: Increase debugability for bad hypercalls

While investigating an issue (in a new codepath I'd introduced, as it turns out), leaving interrupts disabled manifested as a subsequent op in the multicall failing a check_lock() test. The codepath would have hit the ASSERT_NOT_IN_ATOMIC on the return-to-guest path, had it not hit the check_lock(

Re: [Xen-devel] [PATCH] aarch64: advertise the GIC system register interface

On 31 October 2017 at 17:01, Stefano Stabellini wrote: > Fixing QEMU is harder than I expected. Would it be possible to update > id_aa64pfr0 at CPU reset time? Like cpu->id_aa64pfr0 |= 0x0100; ? At that point we've already called register_cp_regs_for_features(), which is where we read cpu->id

Re: [Xen-devel] [PATCH] aarch64: advertise the GIC system register interface

On Tue, 31 Oct 2017, Peter Maydell wrote: > On 19 October 2017 at 15:46, Peter Maydell wrote: > > On 18 October 2017 at 01:10, Stefano Stabellini > > wrote: > >> Advertise the presence of the GIC system register interface (1<<24) > >> according to H9.248 of the ARM ARM. > >> > >> This patch allo

Re: [Xen-devel] Commit moratorium to staging

On Tue, Oct 31, 2017 at 10:49:35AM +, Julien Grall wrote: > Hi all, > > Master lags 15 days behind staging due to tests failing reliably on some of > the hardware in osstest (see [1]). > > At the moment a force push is not feasible because the same tests passes on > different hardware (see [2

[Xen-devel] [qemu-mainline test] 115431: regressions - FAIL

flight 115431 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/115431/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i3866 xen-buildfail REGR. vs. 114507 build-amd64-xsm

Re: [Xen-devel] [PATCH 5/5] docs: add PV sound device config

On Mon, Oct 30, 2017 at 8:00 PM, Marek Marczykowski-Górecki < marma...@invisiblethingslab.com> wrote: > On Mon, Oct 02, 2017 at 12:49:24PM +0300, Oleksandr Grytsov wrote: > > +=item B > > + > > +Short name of the virtual sound card. > > + > > +=item B > > + > > +Long name of the virtual sound card

Re: [Xen-devel] [PATCH] gdbsx: prefer privcmd character device

On Tue, Oct 31, 2017 at 10:20:11AM -0500, Doug Goldstein wrote: > Prefer using the character device over the proc file if the character > device exists. > > CC: Elena Ufimtseva > CC: Ian Jackson > CC: Stefano Stabellini > CC: Wei Liu > Signed-off-by: Doug Goldstein > --- > So this was origina

[Xen-devel] [PATCH] gdbsx: prefer privcmd character device

Prefer using the character device over the proc file if the character device exists. CC: Elena Ufimtseva CC: Ian Jackson CC: Stefano Stabellini CC: Wei Liu Signed-off-by: Doug Goldstein --- So this was originally submitted with 9c89dc95201 and 7d418eab3b6 and was rejected since the goal was t

Re: [Xen-devel] [PATCH 1/5] libxl: add PV sound device

On Mon, Oct 30, 2017 at 7:39 PM, Wei Liu wrote: > On Mon, Oct 02, 2017 at 12:49:20PM +0300, Oleksandr Grytsov wrote: > > From: Oleksandr Grytsov > > > > Add PV sound device described in sndif.h > > > > Signed-off-by: Oleksandr Grytsov > > [...] > > > > libxl__console_backend = Enumeration("con

Re: [Xen-devel] [PATCH 1/5] libxl: add PV sound device

On Tue, Oct 31, 2017 at 04:51:48PM +0200, Oleksandr Grytsov wrote: > > > + > > > +if (params->sample_rates) { > > > +// calculate required string size; > > > > Coding style. > > > Sorry, could you specify more precisely what has to be changed in this > place? > We use /* ... */ for

Re: [Xen-devel] [PATCH 1/5] libxl: add PV sound device

On Mon, Oct 30, 2017 at 7:39 PM, Wei Liu wrote: > On Mon, Oct 02, 2017 at 12:49:20PM +0300, Oleksandr Grytsov wrote: > > From: Oleksandr Grytsov > > > > Add PV sound device described in sndif.h > > > > Signed-off-by: Oleksandr Grytsov > > [...] > > > > libxl__console_backend = Enumeration("con

[Xen-devel] [linux-linus test] 115414: regressions - FAIL

flight 115414 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/115414/ 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. 114682 test-amd64-amd64-xl

Re: [Xen-devel] [RFC] [Draft Design] ACPI/IORT Support in Xen.

On 10/31/2017 5:03 AM, Goel, Sameer wrote: On 10/12/2017 3:03 PM, Manish Jaggi wrote: ACPI/IORT Support in Xen. -- I had sent out patch series [0] to hide smmu from Dom0 IORT. Extending the scope and including all that is required to support ACPI/IORT in Xe

[Xen-devel] [OSSTEST PATCH v2 10/19] ts-debian-fixup: use correct resume device

See code comment for explanation. Signed-off-by: Wei Liu --- ts-debian-fixup | 12 1 file changed, 12 insertions(+) diff --git a/ts-debian-fixup b/ts-debian-fixup index 288766d..9a63c61 100755 --- a/ts-debian-fixup +++ b/ts-debian-fixup @@ -175,6 +175,18 @@ sub otherfixupcfg () {

[Xen-devel] [OSSTEST PATCH v2 12/19] ts-xen-build-prep: install e2fslibs-dev

The in-tree libfsimage ext2fs implementation can't handle 64bit enabled ext4, which is the default in stretch. Installing e2fslibs-dev causes libfsimage to pick up the packaged ext2fs implementation. Signed-off-by: Wei Liu --- ts-xen-build-prep | 6 ++ 1 file changed, 6 insertions(+) diff

[Xen-devel] [OSSTEST PATCH v2 15/19] Add clk_ignore_unused for stretch for arm hosts

Without that parameter we lose uart output. Signed-off-by: Wei Liu --- Osstest/Debian.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm index e7fb020..2bfd5ae 100644 --- a/Osstest/Debian.pm +++ b/Osstest/Debian.pm @@ -240,7 +240,7 @@ END

[Xen-devel] [OSSTEST PATCH v2 19/19] Switch to Debian Stretch

Signed-off-by: Wei Liu --- Osstest.pm| 2 +- production-config | 2 ++ 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/Osstest.pm b/Osstest.pm index ceb62ca..f2e4dfa 100644 --- a/Osstest.pm +++ b/Osstest.pm @@ -86,7 +86,7 @@ our %c = qw( Images images -DebianSui

[Xen-devel] [OSSTEST PATCH v2 13/19] TestSupport: add dpkg option when installing packages

Upgrading configuration file of nbd-client is controlled by dpkg in stretch. Add dpkg option to keep old configuration file(s). Signed-off-by: Wei Liu --- Osstest/TestSupport.pm | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Osstest/TestSupport.pm b/Osstest/TestSupport.pm

[Xen-devel] [OSSTEST PATCH v2 17/19] Skip bootloader installation for arm32 in Stretch

Signed-off-by: Wei Liu --- Osstest/Debian.pm | 5 + 1 file changed, 5 insertions(+) diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm index 2c3bcf4..b2d5007 100644 --- a/Osstest/Debian.pm +++ b/Osstest/Debian.pm @@ -1027,6 +1027,11 @@ END $preseed_file.= (

[Xen-devel] [OSSTEST PATCH v2 16/19] Set mac address in interfaces(5) if force-mac-address is set

ff9e0d8cbd generated a udev rule for setting the mac address. But that udev rule is not copied into the target so reboot after installation will fail. We can copy the udev rule to target system so the reboot after installation works, but then the generated udev rules will end up in initramfs, whic

[Xen-devel] [OSSTEST PATCH v2 18/19] make-flight: don't test pvgrub for Xen XXX

XXX Need to pin down the version of Xen when the upgrade to stretch is complete because osstest configuration is branched for each version. Signed-off-by: Wei Liu --- make-flight | 17 - 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/make-flight b/make-flight index

[Xen-devel] [OSSTEST PATCH v2 11/19] ts-debian-hvm-install: disable new nic naming scheme

This is required to fix nested hvm test. The L1 host is installed by this script. We want the L1 host to not use the new nic naming scheme. Signed-off-by: Wei Liu --- ts-debian-hvm-install | 13 + 1 file changed, 13 insertions(+) diff --git a/ts-debian-hvm-install b/ts-debian-hvm-in

[Xen-devel] [OSSTEST PATCH v2 14/19] ts-guests-nbd-mirror: make it work with stretch

On the server side, only add oldstyle= and port= on Wheezy and Jessie. Stretch doesn't support or need those anymore. On the client side, generate new style configuration file. Signed-off-by: Wei Liu --- ts-guests-nbd-mirror | 47 +++ 1 file changed,

[Xen-devel] [OSSTEST PATCH v2 03/19] ts-xen-build-prep: install packages for suites >jessie

Stubdom build needs texinfo. Libvirt build needs autopoint. QEMU build needs libpciaccess-dev. Signed-off-by: Wei Liu --- ts-xen-build-prep | 4 1 file changed, 4 insertions(+) diff --git a/ts-xen-build-prep b/ts-xen-build-prep index 7718cff..80bfb30 100755 --- a/ts-xen-build-prep +++ b/

[Xen-devel] [OSSTEST PATCH v2 08/19] ts-guests-nbd-mirror: use target_{get, put}file_root to transfter cfg

The original code used target_cmd_output_root which caused a trailing new line to be deleted, which caused libvirt converter to fail. It wasn't discovered until now because we appended too many "\n". Use target_{get,put}file_root to do the job. Signed-off-by: Wei Liu --- ts-guests-nbd-mirror |

[Xen-devel] [OSSTEST PATCH v2 00/19] Upgrade to Stretch

First version of this series can be found at [0]. This version contains workaround for Arndale boards. They are now functional. A bunch of test cases failed: 1. Rumpkernel tests -- I've sent an email to Antti for advice. 2. Windows tests -- They don't look different from normal flights. 3. memd

[Xen-devel] [OSSTEST PATCH v2 01/19] gitignore: ignore vim swap file

Signed-off-by: Wei Liu Acked-by: Ian Jackson --- .gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/.gitignore b/.gitignore index 425506b..f7e5b77 100644 --- a/.gitignore +++ b/.gitignore @@ -1,5 +1,6 @@ *~ *.bak +*.swp tmp *.tmp bisection.ps -- 2.11.0 ___

[Xen-devel] [OSSTEST PATCH v2 02/19] ts-xen-build-prep: only install w3c-dtd-xhtml for suites

That package is not included in Stretch. That package was installed because libvirt build needed it. However libvirt builds fine without it in Stretch. Signed-off-by: Wei Liu --- ts-xen-build-prep | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/ts-xen-build-prep b/ts-xen

[Xen-devel] [OSSTEST PATCH v2 04/19] ts-xen-install: install some packages on stretch

The "route" command is now in that package. libnl is needed when running xl. Signed-off-by: Wei Liu --- ts-xen-install | 3 +++ 1 file changed, 3 insertions(+) diff --git a/ts-xen-install b/ts-xen-install index ec907c5..d4c25c7 100755 --- a/ts-xen-install +++ b/ts-xen-install @@ -57,6 +57,9 @@

[Xen-devel] [OSSTEST PATCH v2 09/19] ts-debian-fixup: merge origin extra= to our own

The original extra= was not removed, so there were two extra= in the resulting config file. It wasn't a problem for xl because the second extra= took precedence. However libvirt tests would only pick up the first extra= -- they worked by chance. Fix this issue by merging the original. Signed-of

[Xen-devel] [OSSTEST PATCH v2 05/19] Debian.pm: use sysvinit-core instead of systemd

Install that packages for suites >wheezy, because they use systemd as the default init. Signed-off-by: Wei Liu --- Osstest/Debian.pm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm index 845027a..e7fb020 100644 --- a/Osstest/Debian.pm +++

[Xen-devel] [OSSTEST PATCH v2 07/19] ts-host-install: don't use the new nic naming scheme

Signed-off-by: Wei Liu Acked-by: Ian Jackson --- ts-host-install | 4 1 file changed, 4 insertions(+) diff --git a/ts-host-install b/ts-host-install index 11c14a7..7339858 100755 --- a/ts-host-install +++ b/ts-host-install @@ -271,6 +271,10 @@ END # why this is repeated. push @ho

[Xen-devel] [OSSTEST PATCH v2 06/19] ts-leak-check: suppress systemd-shim, which leaks in stretch

Signed-off-by: Wei Liu Acked-by: Ian Jackson --- ts-leak-check | 1 + 1 file changed, 1 insertion(+) diff --git a/ts-leak-check b/ts-leak-check index 678d069..41e6245 100755 --- a/ts-leak-check +++ b/ts-leak-check @@ -202,6 +202,7 @@ xenstore /vm xenstore /libxl process .* udevd +process .*

Re: [Xen-devel] [PATCH v3 3/7] libxl: introduce a new structure to represent static shared memory regions

On Thu, Oct 19, 2017 at 10:36:31AM +0800, Zhongze Liu wrote: > Add a new structure to the IDL familiy to represent static shared memory > regions > as proposed in the proposal "Allow setting up shared memory areas between VMs > from xl config file" (see [1]). > > [1] https://lists.xen.org/archive

Re: [Xen-devel] [PATCH v3 1/7] libxc: add xc_domain_remove_from_physmap to wrap XENMEM_remove_from_physmap

On Thu, Oct 19, 2017 at 10:36:29AM +0800, Zhongze Liu wrote: > This is for the proposal "Allow setting up shared memory areas between VMs > from xl config file". See: > > https://lists.xen.org/archives/html/xen-devel/2017-08/msg03242.html > > Then plan is to use XENMEM_add_to_physmap_batch to m

Re: [Xen-devel] [RFC] [Draft Design] ACPI/IORT Support in Xen.

Hi Manish, On 10/31/2017 12:05 PM, Manish Jaggi wrote: On 10/27/2017 7:35 PM, Andre Przywara wrote: When PCI device passthrough is supported, the PCIRC is itself virtual (emulated by Xen). One can have any number of virtual PCIRC  and may be virtual SMMUs. Hence the topology can vary. I think

Re: [Xen-devel] [RFC] [Draft Design] ACPI/IORT Support in Xen.

On 10/27/2017 7:35 PM, Andre Przywara wrote: Hi, Hey Andre, On 25/10/17 09:22, Manish Jaggi wrote: On 10/23/2017 7:27 PM, Andre Przywara wrote: Hi Manish, On 12/10/17 22:03, Manish Jaggi wrote: ACPI/IORT Support in Xen. -- I had sent out patch series

[Xen-devel] [linux-4.9 test] 115411: regressions - FAIL

flight 115411 linux-4.9 real [real] http://logs.test-lab.xenproject.org/osstest/logs/115411/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail REGR. vs. 114814 Tests which did not s

Re: [Xen-devel] [PATCH] aarch64: advertise the GIC system register interface

On 19 October 2017 at 15:46, Peter Maydell wrote: > On 18 October 2017 at 01:10, Stefano Stabellini > wrote: >> Advertise the presence of the GIC system register interface (1<<24) >> according to H9.248 of the ARM ARM. >> >> This patch allows Xen to boot on QEMU aarch64. >> >> Signed-off-by: Ste

Re: [Xen-devel] [RFC] [Draft Design] ACPI/IORT Support in Xen.

Hi Sameer, On 10/30/2017 11:33 PM, Goel, Sameer wrote: On 10/12/2017 3:03 PM, Manish Jaggi wrote: 5. Parsing of IORT in Xen -- I think a Linux like approach will solve the following use cases: 1. Identify the SMMU devices and initialize the devices as needed. 2. API fun

[Xen-devel] [qemu-mainline test] 115421: regressions - trouble: blocked/broken/fail/pass

flight 115421 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/115421/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvopsbroken build-armhf-pvops 4 host-ins

[Xen-devel] [distros-debian-snapshot test] 72400: tolerable FAIL

flight 72400 distros-debian-snapshot real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/72400/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-amd64-current-netinst-pygrub 10 debian-di-install fail like 72348 test-amd64-i386-am

Re: [Xen-devel] [PATCH v5 1/1] xen/time: do not decrease steal time after live migration on xen

On 10/30/2017 11:13 PM, Dongli Zhang wrote: Hi Boris, On 10/31/2017 08:58 AM, Boris Ostrovsky wrote: On 10/30/2017 08:14 PM, Dongli Zhang wrote: Hi Boris, On 10/30/2017 09:34 PM, Boris Ostrovsky wrote: On 10/30/2017 04:03 AM, Dongli Zhang wrote: After guest live migration on xen, steal

Re: [Xen-devel] [PATCH 3/6] libxl: add backend type to vkb

On Mon, Oct 30, 2017 at 8:11 PM, Wei Liu wrote: > On Thu, Oct 05, 2017 at 12:07:08PM +0300, Oleksandr Grytsov wrote: > > From: Oleksandr Grytsov > > > > New field backend_type is added to vkb device > > in order to have QEMU and user space backend > > simultaneously. Each vkb backend shall read

Re: [Xen-devel] [PATCH for-4.10] common/spinlock: Improve the output from check_lock() if it trips

On 10/31/2017 10:49 AM, Andrew Cooper wrote: > If check_lock() triggers, a crash will occur. Instead of simply identifying > "the irq context was different", indicate the expected and current irq > context. > > Signed-off-by: Andrew Cooper Reviewed-by: George Dunlap __

Re: [Xen-devel] [PATCH] MAINTAINERS: Make Christian Lindig maintainer for ocaml tools

On Tue, Oct 17, 2017 at 05:44:11PM +0100, Ian Jackson wrote: > oxenstored is our default implementation of xenstore, for platforms > that have ocaml support. We need it to be maintained. Dave Scott, > the only existing maintainer, has had limited availability. > > Christian has been reveiwing pa

Re: [Xen-devel] [PATCH for-4.10] common/spinlock: Improve the output from check_lock() if it trips

On Tue, Oct 31, 2017 at 10:49:10AM +, Andrew Cooper wrote: > If check_lock() triggers, a crash will occur. Instead of simply identifying > "the irq context was different", indicate the expected and current irq > context. > > Signed-off-by: Andrew Cooper Reviewed-by: Wei Liu __

Re: [Xen-devel] [PATCH v7 for-next 02/12] pci: introduce a type to store a SBDF

On Wed, Oct 18, 2017 at 12:40:24PM +0100, Roger Pau Monne wrote: > That provides direct access to all the members that constitute a SBDF. > The only function switched to use it is hvm_pci_decode_addr, because > it makes following patches simpler. > > Suggested-by: Andrew Cooper > Signed-off-by: R

Re: [Xen-devel] [PATCH v7 for-next 08/12] xen: introduce rangeset_consume_ranges

On Wed, Oct 18, 2017 at 12:40:30PM +0100, Roger Pau Monne wrote: > This function allows to iterate over a rangeset while removing the > processed regions. > > This will be used in order to split processing of large memory areas > when mapping them into the guest p2m. > > Signed-off-by: Roger Pau

[Xen-devel] [libvirt test] 115415: tolerable all pass - PUSHED

flight 115415 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/115415/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt-xsm 14 saverestore-support-checkfail like 115312 test-armhf-armhf-libvirt 14 saveresto

[Xen-devel] [PATCH for-4.10] common/spinlock: Improve the output from check_lock() if it trips

If check_lock() triggers, a crash will occur. Instead of simply identifying "the irq context was different", indicate the expected and current irq context. Signed-off-by: Andrew Cooper --- CC: George Dunlap CC: Jan Beulich CC: Konrad Rzeszutek Wilk CC: Stefano Stabellini CC: Tim Deegan CC:

[Xen-devel] Commit moratorium to staging

Hi all, Master lags 15 days behind staging due to tests failing reliably on some of the hardware in osstest (see [1]). At the moment a force push is not feasible because the same tests passes on different hardware (see [2]). Please avoid committing any more patches unless it is fixing a tes

Re: [Xen-devel] [PATCH 4/4] libxl: move ibxl_devid_to_device_... to LIBXL_DEFINE_DEVID_TO_DEVICE

On Thu, Oct 05, 2017 at 12:30:48PM +0300, Oleksandr Grytsov wrote: > From: Oleksandr Grytsov > > Signed-off-by: Oleksandr Grytsov Acked-by: Wei Liu ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel

Re: [Xen-devel] [PATCH 3/4] libxl: move libxl__device_from_ to LIBXL_DEFINE_DEVICE_FROM_TYPE

On Thu, Oct 05, 2017 at 12:30:47PM +0300, Oleksandr Grytsov wrote: > From: Oleksandr Grytsov > > LIBXL_DEFINE_DEVICE_FROM_TYPE uses libxl__..._devtype.type to > be assigned as device and backend type. > > Signed-off-by: Oleksandr Grytsov Acked-by: Wei Liu

Re: [Xen-devel] [PATCH 2/4] libxl: use libxl__device_kind in LIBXL_DEFINE_UPDATE_DEVID

On Thu, Oct 05, 2017 at 12:30:46PM +0300, Oleksandr Grytsov wrote: > From: Oleksandr Grytsov > > Use libxl__..._devtype.type to update device id. > > Signed-off-by: Oleksandr Grytsov Acked-by: Wei Liu ___ Xen-devel mailing list Xen-devel@lists.xen.

Re: [Xen-devel] [PATCH 1/4] libxl: use libxl__device_kind to get device XS entry

On Thu, Oct 05, 2017 at 12:30:45PM +0300, Oleksandr Grytsov wrote: > From: Oleksandr Grytsov > > On adding to XS name of device is taken from > libxl__device_kind enum. On getting device from XS > the name is hardcoded. It leads to potential > mistmatch errors. The patch is using libxl__device_ki

Re: [Xen-devel] [PATCH 2/4 v3] libxl: Change the type of console_mfn to xen_pfn_t

On Tue, Oct 31, 2017 at 12:25:06PM +0530, Bhupinder Thakur wrote: > Currently the type of console mfn is unsigned long in libxl. This may be > an issue for 32-bit toolstack running on 64-bit Xen, where the pfn are > 64 bit. To ensure that console_mfn can hold any valid 64-bit pfn, the > type of con

Re: [Xen-devel] [PATCH 1/4 v3 for-4.10] libxl: Fix the bug introduced in commit "libxl: use correct type modifier for vuart_gfn"

Change the tag to for-4.10. Julien, this is needed to fix vuart emulation. ___ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel

Re: [Xen-devel] [PATCH 4/4 v3] xenconsole: Define and use a macro XEN_INVALID_PFN instead of -1

On Tue, Oct 31, 2017 at 12:25:08PM +0530, Bhupinder Thakur wrote: > xenconsole will use a new macro XEN_INVALID_PFN instead of -1 for > initializing ring-ref. > Since the type of ring_ref is changed to xen_pfn_t (which is an unsigned > value) assigning -1 > appeared to be confusing. For clarity,

[Xen-devel] [qemu-mainline test] 115417: regressions - FAIL

flight 115417 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/115417/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i3866 xen-buildfail REGR. vs. 114507 build-amd64-xsm

Re: [Xen-devel] [examine test] 115400: regressions - FAIL

On Mon, Oct 30, 2017 at 06:48:46PM +, osstest service owner wrote: > flight 115400 examine real [real] > http://logs.test-lab.xenproject.org/osstest/logs/115400/ > > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > examine-elbling0

[Xen-devel] [xen-unstable test] 115401: regressions - FAIL

flight 115401 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/115401/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stopfail REGR. vs. 114644 test-amd64-amd64-x