Re: [Xen-devel] [PATCH v3 0/5] sndif: add explicit back and front synchronization

ping On 03/27/2018 08:41 AM, Oleksandr Andrushchenko wrote: Hi, Konrad! Could you please review? Thank you, Oleksandr On 03/21/2018 09:25 AM, Oleksandr Andrushchenko wrote: On 03/21/2018 09:20 AM, Takashi Iwai wrote: On Wed, 21 Mar 2018 08:15:36 +0100, Oleksandr Andrushchenko wrote: On

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

flight 121705 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/121705/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-qemuu-nested-intel 14 xen-boot/l1 fail REGR. vs. 120095

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

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

[Xen-devel] [ovmf test] 121710: all pass - PUSHED

flight 121710 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/121710/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 5b91bf82c67b586b9588cbe4bbffa1588f6b5926 baseline version: ovmf

[Xen-devel] [xen-4.9-testing test] 121704: FAIL

flight 121704 xen-4.9-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/121704/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-xtf-amd64-amd64-3 broken in 121358 Tests

[Xen-devel] [xen-4.7-testing test] 121700: FAIL

flight 121700 xen-4.7-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/121700/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-amd64-pvgrub broken in 121444

[Xen-devel] [rumprun test] 121706: regressions - FAIL

flight 121706 rumprun real [real] http://logs.test-lab.xenproject.org/osstest/logs/121706/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-rumprun 6 rumprun-buildfail REGR. vs. 106754 build-i386-rumprun

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

flight 121679 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/121679/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-xsm7 xen-boot fail REGR. vs. 118324

[Xen-devel] [PATCH v1] Xen-blkfront fixes to dynamically adjust ring.

Hi! This patch allows dynamic reconfiguration of the three different parameters that an Xen blkfront driver initially negotiates: * max_indirect_segs: Maximum amount of segments. * max_ring_page_order: Maximum order of pages to be used for the shared ring. * max_queues: Maximum of

[Xen-devel] [PATCH v1] xen-blkfront: dynamic configuration of per-vbd resources

From: Bob Liu The current VBD layer reserves buffer space for each attached device based on three statically configured settings which are read at boot time. * max_indirect_segs: Maximum amount of segments. * max_ring_page_order: Maximum order of pages to be used for the

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

flight 121682 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/121682/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 10 debian-hvm-install fail REGR. vs.

[Xen-devel] [xen-4.6-testing test] 121686: regressions - FAIL

flight 121686 xen-4.6-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/121686/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-qemuu-nested-intel 17 debian-hvm-install/l1/l2 fail REGR. vs. 119227 Tests

[Xen-devel] [RESEND PATCH v5 1/2] libxl: Implement the handler to handle unrecoverable AER errors

Implement the callback function to handle unrecoverable AER errors, and also the public APIs that can be used to register/unregister the handler. When an AER error occurs, the handler will forcibly remove the erring PCIe device from the guest. Signed-off-by: Venu Busireddy

[Xen-devel] [RESEND PATCH v5 0/2] Containing AER unrecoverable errors

This patch set is part of a set of patches that together allow containment of unrecoverable AER errors from PCIe devices assigned to guests in passthrough mode. The containment is achieved by forcibly removing the erring PCIe device from the guest. The original xen-pciback patch corresponding to

Re: [Xen-devel] [PATCH v2 07/17] arm64: vgic-v3: Add ICV_EOIR1_EL1 handler

On 04/02/2018 04:33 PM, Manish Jaggi wrote: On 03/27/2018 03:48 PM, Marc Zyngier wrote: On 27/03/18 10:07, Manish Jaggi wrote: This patch is ported to xen from linux commit b6f49035b4bf6e2709f2a5fed3107f5438c1fd02 KVM: arm64: vgic-v3: Add ICV_EOIR1_EL1 handler Add a handler for writing the

Re: [Xen-devel] [PATCH v2 07/17] arm64: vgic-v3: Add ICV_EOIR1_EL1 handler

On 03/27/2018 03:48 PM, Marc Zyngier wrote: On 27/03/18 10:07, Manish Jaggi wrote: This patch is ported to xen from linux commit b6f49035b4bf6e2709f2a5fed3107f5438c1fd02 KVM: arm64: vgic-v3: Add ICV_EOIR1_EL1 handler Add a handler for writing the guest's view of the ICC_EOIR1_EL1 register.

Re: [Xen-devel] stubdom --disable-pv-grub has not effect

Am Mon, 2 Apr 2018 10:44:23 +0100 schrieb Wei Liu : > I suppose you hit some sort of compile error because pv-grub has rotten? A post-build check scans the build log for warnings. Some of them are seen as fatal, and the otherwise successful build is marked as FAIL, no rpm

Re: [Xen-devel] stubdom --disable-pv-grub has not effect

On Mon, Apr 02, 2018 at 11:40:54AM +0200, Olaf Hering wrote: > On Sun, Apr 01, Wei Liu wrote: > > > No. That's a bug in our build system. > > Thanks. For some reason only gcc48-4.8.3.rpm from SLE_11 is affected, > not gcc43-4.3.4.rpm from SLE_11 nor gcc48-4.8.5.rpm from SLE_12. > This fixes my

Re: [Xen-devel] [PATCH v2] x86/boot: Disable IBRS in intr/nmi exit path at bootup stage

On 2018/3/27 16:52, Jan Beulich wrote: On 27.03.18 at 06:52, wrote: After reset, IBRS is disabled by processor, but a coming intr/nmi leave IBRS enabled after their exit. It's not necessory for bootup code to run in low performance with IBRS enabled. On ORACLE

Re: [Xen-devel] stubdom --disable-pv-grub has not effect

On Sun, Apr 01, Wei Liu wrote: > No. That's a bug in our build system. Thanks. For some reason only gcc48-4.8.3.rpm from SLE_11 is affected, not gcc43-4.3.4.rpm from SLE_11 nor gcc48-4.8.5.rpm from SLE_12. This fixes my packages for the time being: sed -i '/ stubdom install-grub/d' Makefile

Re: [Xen-devel] X86 Community Call - Wed Apr 11, 14:00 - 15:00 UTC - Call for Agenda Items

Hi, Lars, Chao and I will be traveling and thus will miss the meeting. From our side, we propose continue to discuss the features which we didn't cover last time, including SGX, SPP, PT-VMX and 288 vCPU. Best Regards John Ji -Original Message- From: George Dunlap

Re: [Xen-devel] [PATCH v8] new config option vtsc_tolerance_khz to avoid TSC emulation

On Sun, Apr 01, 2018 at 10:29:58PM +0200, Olaf Hering wrote: > Add an option to control when vTSC emulation will be activated for a > domU with tsc_mode=default. Without such option each TSC access from > domU will be emulated, which causes a significant perfomance drop for > workloads that make

Re: [Xen-devel] Need some advices on how to workaround a hardware bug

On Fri, Mar 30, 2018 at 02:23:13AM -0600, Jan Beulich wrote: Chao Gao 03/30/18 7:19 AM >>> >>I met an EPT violation and then the guest was destroyed by Xen >>after assigning a device to the guest. After some investigation, I found >>it is caused by the device isn't a

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

flight 121522 linux-4.9 real [real] http://logs.test-lab.xenproject.org/osstest/logs/121522/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemut-ws16-amd64 16 guest-localmigrate/x10 fail REGR. vs. 121371 Tests which