Memory coherency issue with IO thread offloading?

Thanks Jens, Nick, Christophe and Michael for your work so far. Apologies for the out of thread email. Confirming MariabD-10.6+ is required( when we added liburing), and previous versions used libaio (which tested without incident as mpe retested). We were (we're now back on the old good kernel

Re: [PATCH] powerpc/fault: kernel can extend a user process's stack

%1 danielgb@ozrom2:~$ signal delivered, stack base 0x7f63 top 0x7f501057 (1241001 used) [1]+ Done./a.out 1241000 danielgb@ozrom2:~$ uname -a Linux ozrom2 5.5.0-rc1-1-g83ab444248c1 #1 SMP Wed Dec 11 17:01:50 AEDT 2019 ppc64le ppc64le ppc64le GN

Re: [PATCH] pseries/drmem: Check for zero filled ibm, dynamic-memory property.

Looks good to me. Boots without backtrace. qemu-system-ppc64 -enable-kvm -cpu POWER8 -m 4G -M pseries -nographic -vga none -kernel /tmp/vmlinux qemu-system-ppc64 --version QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.20) Tested-by: Daniel Black

Re: [PATCH] KVM: KVM_MAX_IRQ_ROUTES only defined with CONFIG_HAVE_KVM_IRQ_ROUTING

Apologies, just noticed 95e2a3b3ef177730019e3799917193595133b275 being the revert of 36ae3c0a36b7 On 20/09/17 11:31, Daniel Black wrote: > Commit 36ae3c0a36b7 introduced code using KVM_MAX_IRQ_ROUTES. This > define isn't available on all platforms. As it is d

[PATCH] KVM: KVM_MAX_IRQ_ROUTES only defined with CONFIG_HAVE_KVM_IRQ_ROUTING

via KVM_IRQFD") Reported-by: Abdul Haleem Suggested-by: Jan H. Schönherr Signed-off-by: Daniel Black --- virt/kvm/eventfd.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/virt/kvm/eventfd.c b/virt/kvm/eventfd.c index c608ab4..75910dd 100644 --- a/virt/kvm/eventfd.c +++ b/virt/kvm

Power8 host unusable after kvm VM guest suspended for 2+ mins with client networking traffic

Further testing of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714859 root@p87:~# virsh start jenkins-ppc64 Domain jenkins-ppc64 started root@p87:~# uname -a Linux p87 4.13.0 #1 SMP Sun Sep 3 22:39:51 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@p87:~# uptime 14:09:29 up 7 min,

oops: arch_update_cpu_topology -> lockdep_assert_cpus_held

4.13-rc3 mainline at b1b6f83ac938d176742c85757960dec2cf10e468 Backtrace occurred for every CPU during boot. its a kvm host machine. [ 254.131688] new mount options do not match the existing superblock, will be ignored [ 255.654622] [ cut here ] [ 255.654658] WARNING: CP

4.13.0-next-20170904 WARNING: possible circular locking dependency detected

found on booting. kvm bare metal host machine. == WARNING: possible circular locking dependency detected 4.13.0-next-20170904 #1 Tainted: GW -- ppc64_cpu/4940 is trying to acquire lock