qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Eduardo Habkost" <ehabkost@redhat.com>,
	kvm@vger.kernel.org, "Gleb Natapov" <gleb@kernel.org>,
	qemu-devel@nongnu.org,
	"Andrey Smetanin" <asmetanin@virtuozzo.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v6 0/12] HyperV equivalent of pvpanic driver
Date: Wed, 12 Aug 2015 14:54:33 +0300	[thread overview]
Message-ID: <55CB33F9.8050608@openvz.org> (raw)
In-Reply-To: <559BA807.5080201@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2383 bytes --]

On 07/07/2015 01:20 PM, Paolo Bonzini wrote:
>
> On 03/07/2015 14:01, Denis V. Lunev wrote:
>> 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 provide functionality equal to pvpanic device without
>> QEMU guest agent for Windows.
>>
>> The idea is borrowed from Linux HyperV bus driver and validated against
>> Windows 2k12.
>>
>> Changes from v5:
>> * added hyperv crash msrs into supported/emulated list
>> * qemu: reset CPUState::crash_occurred at cpu reset
>> * qemu: userspace checks kernel support of hyperv crash msrs
>>    by kvm_get_supported_msrs
>>
>> Changes from v4:
>> * fixed typo in email of Andreas Färber <afaerber@suse.de>
>>    my vim strangely behaves on lines with extended Deutch chars
>>
>> Changes from v3:
>> * remove unused HV_X64_MSR_CRASH_CTL_NOTIFY
>> * added documentation section about KVM_SYSTEM_EVENT_CRASH
>> * allow only supported values inside crash ctl msr
>> * qemu: split patch into generic crash handling patches and hyperv specific
>> * qemu: skip migration of crash ctl msr value
>>
>> Changes from v2:
>> * forbid modification crash ctl msr by guest
>> * qemu_system_guest_panicked usage in pvpanic and s390x
>> * hyper-v crash handler move from generic kvm to i386
>> * hyper-v crash handler: skip fetching crash msrs just mark crash occurred
>> * sync with linux-next 20150629
>> * patch 11 squashed to patch 10
>> * patch 9 squashed to patch 7
>>
>> Changes from v1:
>> * hyperv code move to hyperv.c
>> * added read handlers of crash data msrs
>> * added per vm and per cpu hyperv context structures
>> * added saving crash msrs inside qemu cpu state
>> * added qemu fetch and update of crash msrs
>> * added qemu crash msrs store in cpu state and it's migration
>>
>> Signed-off-by: Andrey Smetanin <asmetanin@virtuozzo.com>
>> Signed-off-by: Denis V. Lunev <den@openvz.org>
>> CC: Gleb Natapov <gleb@kernel.org>
>> CC: Paolo Bonzini <pbonzini@redhat.com>
>>
> I'm queuing patches 1-8 to the KVM tree.  For patch 9-12, I've applied
> them locally but would like Eduardo or Andreas to ack 11 and 12.
>
> Paolo
guys?

we are going to move forward with other HyperV bits.

Den

[-- Attachment #2: Type: text/html, Size: 3114 bytes --]

  reply	other threads:[~2015-08-12 11:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 12:01 [Qemu-devel] [PATCH v6 0/12] HyperV equivalent of pvpanic driver Denis V. Lunev
2015-07-03 12:01 ` [Qemu-devel] [PATCH 1/12] kvm/x86: move Hyper-V MSR's/hypercall code into hyperv.c file Denis V. Lunev
2015-07-03 12:01 ` [Qemu-devel] [PATCH 2/12] kvm: introduce vcpu_debug = kvm_debug + vcpu context Denis V. Lunev
2015-07-03 12:01 ` [Qemu-devel] [PATCH 3/12] kvm: add hyper-v crash msrs values Denis V. Lunev
2015-07-03 12:01 ` [Qemu-devel] [PATCH 4/12] kvm/x86: added hyper-v crash msrs into kvm hyperv context Denis V. Lunev
2015-07-03 12:01 ` [Qemu-devel] [PATCH 5/12] kvm: added KVM_REQ_HV_CRASH value to notify qemu about hyper-v crash Denis V. Lunev
2015-07-03 12:01 ` [Qemu-devel] [PATCH 6/12] kvm/x86: mark hyper-v crash msrs as partition wide Denis V. Lunev
2015-07-03 12:01 ` [Qemu-devel] [PATCH 7/12] kvm/x86: added hyper-v crash data and ctl msr's get/set'ers Denis V. Lunev
2015-08-19  0:41   ` Wanpeng Li
2015-08-19  0:47     ` Denis V. Lunev
2015-07-03 12:01 ` [Qemu-devel] [PATCH 8/12] kvm/x86: add sending hyper-v crash notification to user space Denis V. Lunev
2015-07-03 12:01 ` [Qemu-devel] [PATCH 09/12] Added generic panic handler qemu_system_guest_panicked() Denis V. Lunev
2015-07-03 12:01 ` [Qemu-devel] [PATCH 10/12] kvm: Add kvm system event crash handler Denis V. Lunev
2015-07-03 12:01 ` [Qemu-devel] [PATCH 11/12] cpu: Add crash_occurred flag into CPUState Denis V. Lunev
2015-09-02 21:13   ` Paolo Bonzini
2015-07-03 12:01 ` [Qemu-devel] [PATCH 12/12] i386/kvm: Hyper-v crash msrs set/get'ers and migration Denis V. Lunev
2015-07-07 10:19   ` Paolo Bonzini
2015-07-07 10:21   ` Paolo Bonzini
2015-07-07 10:20 ` [Qemu-devel] [PATCH v6 0/12] HyperV equivalent of pvpanic driver Paolo Bonzini
2015-08-12 11:54   ` Denis V. Lunev [this message]
2015-08-12 12:47     ` Paolo Bonzini
2015-08-12 13:22       ` Denis V. Lunev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55CB33F9.8050608@openvz.org \
    --to=den@openvz.org \
    --cc=afaerber@suse.de \
    --cc=asmetanin@virtuozzo.com \
    --cc=ehabkost@redhat.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).