From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Andrey Smetanin <asmetanin@virtuozzo.com>,
"Denis V. Lunev" <den@openvz.org>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH 11/11] qemu/kvm: mark in cpu state that hyper-v crash occured
Date: Mon, 22 Jun 2015 19:46:58 +0200 [thread overview]
Message-ID: <55884A12.2020806@suse.de> (raw)
In-Reply-To: <558839A9.9040009@redhat.com>
Am 22.06.2015 um 18:36 schrieb Paolo Bonzini:
> On 22/06/2015 18:33, Andreas Färber wrote:
>>>> On the other hand, I wonder if current_cpu is available in
>>>> qemu_system_guest_panicked. If so, you could add the field to the
>>>> generic CPUState struct and migrate it as a subsection of
>>>> vmstate_cpu_common.
>> Hm, not sure whether it is.
>
> It should be...
Obviously depends on the call site. :) At some point in cpu-exec.c,
current_cpu gets set to NULL. So the function would at least deserve a
comment on when (not to) use it.
Cheers,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB
21284 (AG Nürnberg)
WARNING: multiple messages have this Message-ID (diff)
From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Andrey Smetanin <asmetanin@virtuozzo.com>,
"Denis V. Lunev" <den@openvz.org>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 11/11] qemu/kvm: mark in cpu state that hyper-v crash occured
Date: Mon, 22 Jun 2015 19:46:58 +0200 [thread overview]
Message-ID: <55884A12.2020806@suse.de> (raw)
In-Reply-To: <558839A9.9040009@redhat.com>
Am 22.06.2015 um 18:36 schrieb Paolo Bonzini:
> On 22/06/2015 18:33, Andreas Färber wrote:
>>>> On the other hand, I wonder if current_cpu is available in
>>>> qemu_system_guest_panicked. If so, you could add the field to the
>>>> generic CPUState struct and migrate it as a subsection of
>>>> vmstate_cpu_common.
>> Hm, not sure whether it is.
>
> It should be...
Obviously depends on the call site. :) At some point in cpu-exec.c,
current_cpu gets set to NULL. So the function would at least deserve a
comment on when (not to) use it.
Cheers,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB
21284 (AG Nürnberg)
next prev parent reply other threads:[~2015-06-22 17:46 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 16:04 [PATCH v2 0/11] HyperV equivalent of pvpanic driver Denis V. Lunev
2015-06-22 16:04 ` [Qemu-devel] " Denis V. Lunev
2015-06-22 16:04 ` [PATCH 01/11] kvm/x86: move Hyper-V MSR's/hypercall code into hyperv.c file Denis V. Lunev
2015-06-22 16:04 ` [Qemu-devel] " Denis V. Lunev
2015-06-25 10:25 ` Denis V. Lunev
2015-06-25 10:25 ` [Qemu-devel] " Denis V. Lunev
2015-06-25 10:26 ` Paolo Bonzini
2015-06-25 10:26 ` [Qemu-devel] " Paolo Bonzini
2015-06-22 16:04 ` [PATCH 02/11] kvm: introduce vcpu_debug = kvm_debug + vcpu context Denis V. Lunev
2015-06-22 16:04 ` [Qemu-devel] " Denis V. Lunev
2015-06-22 16:05 ` [PATCH 03/11] kvm: add hyper-v crash msrs constants Denis V. Lunev
2015-06-22 16:05 ` [Qemu-devel] " Denis V. Lunev
2015-06-22 16:05 ` [PATCH 04/11] kvm/x86: added hyper-v crash msrs into kvm hyperv context Denis V. Lunev
2015-06-22 16:05 ` [Qemu-devel] " Denis V. Lunev
2015-06-22 16:05 ` [PATCH 05/11] kvm: added KVM_REQ_HV_CRASH value to notify qemu about Hyper-V crash Denis V. Lunev
2015-06-22 16:05 ` [Qemu-devel] " Denis V. Lunev
2015-06-22 16:05 ` [PATCH 06/11] kvm/x86: mark hyper-v crash msrs as partition wide Denis V. Lunev
2015-06-22 16:05 ` [Qemu-devel] " Denis V. Lunev
2015-06-22 16:05 ` [PATCH 07/11] kvm/x86: added hyper-v crash data and ctl msr's get/set'ers Denis V. Lunev
2015-06-22 16:05 ` [Qemu-devel] " Denis V. Lunev
2015-06-22 23:52 ` Peter Hornyack
2015-06-22 23:52 ` [Qemu-devel] " Peter Hornyack
2015-06-23 9:47 ` Denis V. Lunev
2015-06-23 9:47 ` [Qemu-devel] " Denis V. Lunev
2015-06-23 9:51 ` Paolo Bonzini
2015-06-23 9:51 ` [Qemu-devel] " Paolo Bonzini
2015-06-23 10:08 ` Denis V. Lunev
2015-06-23 10:08 ` [Qemu-devel] " Denis V. Lunev
2015-06-23 10:30 ` Paolo Bonzini
2015-06-23 10:30 ` [Qemu-devel] " Paolo Bonzini
2015-06-22 16:05 ` [PATCH 08/11] kvm/x86: add sending hyper-v crash notification to user space Denis V. Lunev
2015-06-22 16:05 ` [Qemu-devel] " Denis V. Lunev
2015-06-22 16:05 ` [PATCH 09/11] kvm/x86: distingiush hyper-v guest crash notification Denis V. Lunev
2015-06-22 16:05 ` [Qemu-devel] " Denis V. Lunev
2015-06-22 16:09 ` Paolo Bonzini
2015-06-22 16:09 ` [Qemu-devel] " Paolo Bonzini
2015-06-22 23:55 ` Peter Hornyack
2015-06-22 23:55 ` [Qemu-devel] " Peter Hornyack
2015-06-23 9:52 ` Paolo Bonzini
2015-06-23 9:52 ` [Qemu-devel] " Paolo Bonzini
2015-06-22 16:05 ` [PATCH 10/11] qemu/kvm: kvm hyper-v based guest crash event handling Denis V. Lunev
2015-06-22 16:05 ` [Qemu-devel] " Denis V. Lunev
2015-06-22 16:15 ` Paolo Bonzini
2015-06-22 16:15 ` [Qemu-devel] " Paolo Bonzini
2015-06-22 16:17 ` Paolo Bonzini
2015-06-22 16:17 ` [Qemu-devel] " Paolo Bonzini
2015-06-22 16:05 ` [PATCH 11/11] qemu/kvm: mark in cpu state that hyper-v crash occured Denis V. Lunev
2015-06-22 16:05 ` [Qemu-devel] " Denis V. Lunev
2015-06-22 16:23 ` Andreas Färber
2015-06-22 16:23 ` [Qemu-devel] " Andreas Färber
2015-06-22 16:27 ` Paolo Bonzini
2015-06-22 16:27 ` [Qemu-devel] " Paolo Bonzini
2015-06-22 16:33 ` Andreas Färber
2015-06-22 16:33 ` [Qemu-devel] " Andreas Färber
2015-06-22 16:35 ` Denis V. Lunev
2015-06-22 16:35 ` [Qemu-devel] " Denis V. Lunev
2015-06-22 16:36 ` Paolo Bonzini
2015-06-22 16:36 ` [Qemu-devel] " Paolo Bonzini
2015-06-22 17:46 ` Andreas Färber [this message]
2015-06-22 17:46 ` Andreas Färber
2015-06-23 9:53 ` Paolo Bonzini
2015-06-23 9:53 ` [Qemu-devel] " Paolo Bonzini
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=55884A12.2020806@suse.de \
--to=afaerber@suse.de \
--cc=asmetanin@virtuozzo.com \
--cc=den@openvz.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.