From: Joerg Roedel <joro@8bytes.org>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
Gleb Natapov <gleb@redhat.com>,
Nadav Har'El <nyh@math.technion.ac.il>,
"Nakajima, Jun" <jun.nakajima@intel.com>,
kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] KVM: nSVM/nVMX: Implement vmexit on INIT assertion
Date: Wed, 27 Feb 2013 12:17:27 +0100 [thread overview]
Message-ID: <20130227111727.GF26252@8bytes.org> (raw)
In-Reply-To: <512A1EF5.2070709@web.de>
On Sun, Feb 24, 2013 at 03:08:53PM +0100, Jan Kiszka wrote:
> From: Jan Kiszka <jan.kiszka@siemens.com>
> @@ -2390,6 +2390,21 @@ static int nested_svm_vmexit(struct vcpu_svm *svm)
> return 0;
> }
> +static bool nested_svm_handle_init_received(struct kvm_vcpu *vcpu)
> +{
> + struct vcpu_svm *svm = to_svm(vcpu);
> +
> + if (!is_guest_mode(vcpu) ||
> + !(svm->nested.intercept & (1ULL << INTERCEPT_INIT)))
> + return false;
> +
> + svm->vmcb->control.exit_code = SVM_EXIT_INIT;
> + svm->vmcb->control.exit_int_info = 0;
> + nested_svm_vmexit(svm);
> +
> + return true;
> +}
[...]
> + if (vcpu->arch.mp_state == KVM_MP_STATE_INIT_RECEIVED &&
> + kvm_x86_ops->handle_init_received(vcpu)) {
> + /* nested vmexit, L1 is runnable now */
> + vcpu->arch.mp_state = KVM_MP_STATE_RUNNABLE;
> + return 1;
> + }
Hmm, looks like the INIT signal is lost after the VMEXIT. But on SVM the
INIT signal is still pending an will be delivered when GIF becomes one
again. Do I miss anything?
Joerg
next prev parent reply other threads:[~2013-02-27 11:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 14:08 [PATCH] KVM: nSVM/nVMX: Implement vmexit on INIT assertion Jan Kiszka
2013-02-25 8:00 ` Nadav Har'El
2013-02-25 9:04 ` Jan Kiszka
2013-02-27 11:20 ` Joerg Roedel
2013-02-27 11:23 ` Jan Kiszka
2013-02-27 11:17 ` Joerg Roedel [this message]
2013-02-27 11:22 ` Jan Kiszka
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=20130227111727.GF26252@8bytes.org \
--to=joro@8bytes.org \
--cc=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--cc=jun.nakajima@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=nyh@math.technion.ac.il \
/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.