From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH] fix "info cpus" halted state display
Date: Sun, 23 May 2010 14:26:07 +0300 [thread overview]
Message-ID: <4BF910CF.1080500@redhat.com> (raw)
In-Reply-To: <20100520101617.GE15750@redhat.com>
On 05/20/2010 01:16 PM, Gleb Natapov wrote:
> On Thu, May 13, 2010 at 04:17:14PM +0300, Gleb Natapov wrote:
>
>> When in-kernel irqchip is used env->halted is never used for anything
>> except "info cpus" command. Halted state is synced in
>> kvm_arch_save_mpstate() and showed by do_info_cpus() but otherwise never
>> looked at. Zeroing it here breaks "info cpus" since before
>> do_info_cpus() outputs env->halted in io thread it is zeroed here when
>> vcpu thread reenters kernel.
>>
>>
> Avi, what about this patch?
>
>
Sorry, missed. Applied now.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-05-23 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 13:17 [PATCH] fix "info cpus" halted state display Gleb Natapov
2010-05-13 13:57 ` Jan Kiszka
2010-05-16 5:35 ` Gleb Natapov
2010-05-20 10:16 ` Gleb Natapov
2010-05-23 11:26 ` Avi Kivity [this message]
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=4BF910CF.1080500@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.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 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.