public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] KVM: x86: Rework INIT and SIPI handling
Date: Wed, 13 Mar 2013 12:36:58 +0100	[thread overview]
Message-ID: <514064DA.1080009@siemens.com> (raw)
In-Reply-To: <51405FFD.2040102@siemens.com>

On 2013-03-13 12:16, Jan Kiszka wrote:
>>> @@ -5871,8 +5867,8 @@ static int __vcpu_run(struct kvm_vcpu *vcpu)
>>>                       srcu_read_unlock(&kvm->srcu, vcpu->srcu_idx);
>>>                       kvm_vcpu_block(vcpu);
>>>                       vcpu->srcu_idx = srcu_read_lock(&kvm->srcu);
>>> -                     if (kvm_check_request(KVM_REQ_UNHALT, vcpu))
>>> -                     {
>>> +                     if (kvm_check_request(KVM_REQ_UNHALT, vcpu)) {
>>> +                             kvm_apic_accept_events(vcpu);
>> I think we can drop this. If INIT happens while vcpu is halted it will
>> become runnable here and kvm_apic_accept_events() will be called in
>> vcpu_enter_guest().
> 
> I'm not that sure, but I will recheck carefully.

Doesn't work: If the state was INIT_RECEIVED, we will not process the
SIPI but reenter kvm_vcpu_block. And it's more consistent to process the
events here IMHO.

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2013-03-13 11:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-13  8:50 [PATCH] KVM: x86: Rework INIT and SIPI handling Jan Kiszka
2013-03-13 10:31 ` Gleb Natapov
2013-03-13 11:16   ` Jan Kiszka
2013-03-13 11:36     ` Jan Kiszka [this message]
2013-03-13 12:29       ` Gleb Natapov
2013-03-13 12:40         ` Jan Kiszka
2013-03-13 12:48           ` Gleb Natapov
2013-03-13 12:58             ` Jan Kiszka
2013-03-13 13:18               ` Gleb Natapov
2013-03-13 12:16     ` Gleb Natapov
2013-03-13 12:17       ` Jan Kiszka
2013-03-13 12:22         ` Gleb Natapov
2013-03-13 11:10 ` Paolo Bonzini
2013-03-13 11:20   ` 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=514064DA.1080009@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox