From: Avi Kivity <avi@qumranet.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [patch 0/2] do not run halted vcpu's
Date: Wed, 13 Aug 2008 13:44:33 +0300 [thread overview]
Message-ID: <48A2BB11.2020909@qumranet.com> (raw)
In-Reply-To: <20080801230912.013317832@localhost.localdomain>
Marcelo Tosatti wrote:
> Avi Kivity wrote:
>
>
>> Any reason this is not in __vcpu_run()?
>>
>> Our main loop could look like
>>
>> while (no reason to stop)
>> if (runnable)
>> enter guest
>> else
>> block
>> deal with aftermath
>>
>> kvm_emulate_halt would then simply modify the mp state.
>>
>
> Like this?
>
> - I don't think it is necessary to test for pending signals inside irq
> safe section, so move that to exit processing.
>
>
It is. We may have received a signal after ioctl processing started but
before entry. If we don't don't check before entry, nothing ensures
we'll ever exit (or we may exit due to some other reason, but the exit
will be delayed).
> - Same for need_resched().
>
>
Incorrect for the same reason. There's no guarantee we will ever exit
if we ignore the rescheduling IPI.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-08-13 10:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 23:09 [patch 0/2] do not run halted vcpu's Marcelo Tosatti
2008-08-01 23:09 ` [patch 1/2] KVM: x86: set debug registers after "schedulable" section Marcelo Tosatti
2008-08-13 10:46 ` Avi Kivity
2008-08-01 23:09 ` [patch 2/2] KVM: x86: do not execute halted vcpus (v2) Marcelo Tosatti
2008-08-13 10:51 ` Avi Kivity
2008-08-13 10:53 ` Avi Kivity
2008-08-13 10:44 ` Avi Kivity [this message]
2008-08-15 0:19 ` [patch 0/2] do not run halted vcpu's Marcelo Tosatti
2008-08-17 6:31 ` Avi Kivity
2008-08-17 7:41 ` Avi Kivity
2008-08-19 23:07 ` Marcelo Tosatti
2008-08-20 4:04 ` Avi Kivity
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=48A2BB11.2020909@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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