[Devel] [PATCH rh7 4/7] ms/kvm/x86: Move Hyper-V specific fields into new per vm/vcpu Hyper-V structures

ms commit - e83d58874ba1de74c13d3c6b05f95a023c860d25 Signed-off-by: Andrey Smetanin Signed-off-by: Denis V. Lunev Reviewed-by: Peter Hornyack CC: Paolo Bonzini CC: Gleb Natapov

Re: [Devel] [PATCH rh7] tcache: do not try to create node if we are not going to store page

On 25.09.2015 15:14, Vladimir Davydov wrote: > Currently, we try to create a tcache node even if we are not going to > actually store a page in tcache (tcache is disabled or we are called by > global reclaimer). This is suboptimal, because we will drop the node > anyway then. > > Signed-off-by:

[Devel] [PATCH rh7 6/7] ms/KVM: Add KVM_EXIT_SYSTEM_EVENT to user space API header

From: Anup Patel Currently, we don't have an exit reason to notify user space about a system-level event (for e.g. system reset or shutdown) triggered by the VCPU. This patch adds exit reason KVM_EXIT_SYSTEM_EVENT for this purpose. We can also inform user space about the

[Devel] [PATCH rh7 5/7] ms/kvm/x86: added hyper-v crash msrs into kvm hyperv context

Added kvm Hyper-V context hv crash variables as storage of Hyper-V crash msrs. ms commit - e7d9513b60e87f62e41090fa3a26eca796924346 Signed-off-by: Andrey Smetanin Signed-off-by: Denis V. Lunev Reviewed-by: Peter Hornyack CC:

[Devel] [PATCH rh7 1/7] ms/kvm: add hyper-v crash msrs values

Added Hyper-V crash msrs values - HV_X64_MSR_CRASH*. ms commit - a88464a8b0ffb2f8dfb69d3ab982169578b50f22 Signed-off-by: Andrey Smetanin Signed-off-by: Denis V. Lunev Reviewed-by: Peter Hornyack CC: Paolo Bonzini

[Devel] [PATCH rh7 7/7] ms/kvm/x86: add sending hyper-v crash notification to user space

Sending of notification is done by exiting vcpu to user space if KVM_REQ_HV_CRASH is enabled for vcpu. At exit to user space the kvm_run structure contains system_event with type KVM_SYSTEM_EVENT_CRASH to notify about guest crash occurred. ms commit - 2ce7918990641b07e70e1b25752d666369e2016e

[Devel] [PATCH rh7 0/7] Hyper-V pvpanic equivalent

Windows 2012 guests can notify hypervisor about occurred guest crash (Windows bugcheck(BSOD)) by writing specific Hyper-V msrs. This patch does handling of this MSR's by KVM and sending notification to user space that allows to gather Windows guest crash dump by QEMU/LIBVIRT. The idea is to

[Devel] [PATCH rh7 3/7] ms/kvm: introduce vcpu_debug = kvm_debug + vcpu context

vcpu_debug is useful macro like kvm_debug but additionally includes vcpu context inside output. ms commit - ee86dbc6e327062396748162b95309388c19faab Signed-off-by: Andrey Smetanin Signed-off-by: Denis V. Lunev Reviewed-by: Peter Hornyack

Re: [Devel] [RH7 PATCH] ext4: drop pfcache csum on fallocate

Dmitry Monakhov writes: Please ignore this patch, use second version instead > If fallocate will change file's data we have to drop csum. > > Signed-off-by: Dmitry Monakhov > --- > fs/ext4/extents.c |5 + > 1 files changed, 5 insertions(+), 0

[Devel] [RH7 PATCH] ext4: drop pfcache csum on fallocate V2

>From 83ea3af40033e4214383a9846d8180d9c096c2e0 Mon Sep 17 00:00:00 2001 From: Dmitry Monakhov Date: Tue, 29 Sep 2015 14:35:25 +0400 Subject: [RH7 PATCH] ext4: drop pfcache csum on fallocate v2 If fallocate will change file's data we have to drop csum.

Re: [Devel] [RH7 PATCH] ext4: drop pfcache csum on fallocate V2

Maxim, please review the patch. -- Best regards, Konstantin Khorenko, Virtuozzo Linux Kernel Team On 09/29/2015 01:38 PM, Dmitry Monakhov wrote: ___ Devel mailing list Devel@openvz.org https://lists.openvz.org/mailman/listinfo/devel

[Devel] [PATCH rh7 2/7] ms/kvm/x86: move Hyper-V MSR's/hypercall code into hyperv.c file

This patch introduce Hyper-V related source code file - hyperv.c and per vm and per vcpu hyperv context structures. All Hyper-V MSR's and hypercall code moved into hyperv.c. All Hyper-V kvm/vcpu fields moved into appropriate hyperv context structures. Copyrights and authors information copied from

Re: [Devel] [RH7 PATCH] ext4: drop pfcache csum on fallocate V2

ACK. Dima, this is very minor, but nevertheless -- please write short description of what changed next time. (it takes a while for a reader to find out that s/EXT4_STATE_CSUM/EXT4_STATE_PFCACHE_CSUM is the only change you did since v1) Thanks, Maxim On 09/29/2015 03:38 AM, Dmitry Monakhov