From: Paolo Bonzini <pbonzini@redhat.com>
To: asmetanin@virtuozzo.com
Cc: "Denis V. Lunev" <den@openvz.org>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 9/9] qemu/kvm: kvm hyper-v based guest crash event handling
Date: Thu, 2 Jul 2015 15:30:26 +0200 [thread overview]
Message-ID: <55953CF2.20700@redhat.com> (raw)
In-Reply-To: <1435843180.21037.13.camel@virtuozzo.com>
On 02/07/2015 15:19, Andrey Smetanin wrote:
>>> > > + if (has_msr_hv_crash) {
>>> > > + env->msr_hv_crash_ctl = HV_X64_MSR_CRASH_CTL_NOTIFY;
>> >
>> > The value is always host-defined, so I think it doesn't need a field in
>> > CPUX86State. On the other hand, this:
> Kernel just works with that value, kernel doesn't setup it.
> The user space is allowed to setup this msr if qemu option "hv-crash" is
> on. So the code "env->msr_hv_crash_ctl = HV_X64_MSR_CRASH_CTL_NOTIFY;"
> setups msr in user space at cpu reset. When cpu setup it's registers
> these msr's values are uploaded into kernel.
>
> Anyway we need a code that initially set up crash ctl msr with value
> HV_X64_MSR_CRASH_CTL_NOTIFY. And I think that code should be user space.
> Any objections ?
Yes, that's correct.
What I'm saying, is that the value can be hard-coded and doesn't need a
field in CPUX86State. If you want to leave the field that's also okay,
but even then it should not be part of the migration state.
Paolo
next prev parent reply other threads:[~2015-07-02 13:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-30 11:33 [Qemu-devel] [PATCH v3 0/9] HyperV equivalent of pvpanic driver Denis V. Lunev
2015-06-30 11:33 ` [Qemu-devel] [PATCH 1/9] kvm/x86: move Hyper-V MSR's/hypercall code into hyperv.c file Denis V. Lunev
2015-07-01 0:11 ` Peter Hornyack
2015-06-30 11:33 ` [Qemu-devel] [PATCH 2/9] kvm: introduce vcpu_debug = kvm_debug + vcpu context Denis V. Lunev
2015-07-01 0:12 ` Peter Hornyack
2015-06-30 11:33 ` [Qemu-devel] [PATCH 3/9] kvm: add hyper-v crash msrs values Denis V. Lunev
2015-07-01 0:14 ` Peter Hornyack
2015-07-01 15:00 ` Paolo Bonzini
2015-07-01 15:53 ` Denis V. Lunev
2015-07-01 16:06 ` Peter Hornyack
2015-07-01 16:48 ` Paolo Bonzini
2015-06-30 11:33 ` [Qemu-devel] [PATCH 4/9] kvm/x86: added hyper-v crash msrs into kvm hyperv context Denis V. Lunev
2015-07-01 0:14 ` Peter Hornyack
2015-06-30 11:33 ` [Qemu-devel] [PATCH 5/9] kvm: added KVM_REQ_HV_CRASH value to notify qemu about hyper-v crash Denis V. Lunev
2015-07-01 0:14 ` Peter Hornyack
2015-06-30 11:33 ` [Qemu-devel] [PATCH 6/9] kvm/x86: mark hyper-v crash msrs as partition wide Denis V. Lunev
2015-07-01 0:15 ` Peter Hornyack
2015-06-30 11:33 ` [Qemu-devel] [PATCH 7/9] kvm/x86: added hyper-v crash data and ctl msr's get/set'ers Denis V. Lunev
2015-07-01 0:15 ` Peter Hornyack
2015-07-01 16:47 ` Paolo Bonzini
2015-06-30 11:33 ` [Qemu-devel] [PATCH 8/9] kvm/x86: add sending hyper-v crash notification to user space Denis V. Lunev
2015-07-01 0:16 ` Peter Hornyack
2015-07-01 15:12 ` Paolo Bonzini
2015-06-30 11:33 ` [Qemu-devel] [PATCH 9/9] qemu/kvm: kvm hyper-v based guest crash event handling Denis V. Lunev
2015-07-01 15:07 ` Paolo Bonzini
2015-07-02 13:19 ` Andrey Smetanin
2015-07-02 13:30 ` Paolo Bonzini [this message]
2015-06-30 12:26 ` [Qemu-devel] [PATCH v3 0/9] HyperV equivalent of pvpanic driver Daniel P. Berrange
2015-06-30 12:38 ` Denis V. Lunev
2015-07-01 14:09 ` Paolo Bonzini
2015-07-01 15:55 ` 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=55953CF2.20700@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=asmetanin@virtuozzo.com \
--cc=den@openvz.org \
--cc=kvm@vger.kernel.org \
--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).