From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [patch uq/master 5/9] kvm: synchronize state from cpu context Date: Thu, 06 May 2010 14:31:35 +0300 Message-ID: <4BE2A897.7050303@redhat.com> References: <20100504124518.979470863@redhat.com> <20100504124634.399797233@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org To: Marcelo Tosatti Return-path: Received: from mx1.redhat.com ([209.132.183.28]:36241 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751522Ab0EFLbj (ORCPT ); Thu, 6 May 2010 07:31:39 -0400 In-Reply-To: <20100504124634.399797233@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 05/04/2010 03:45 PM, Marcelo Tosatti wrote: > From: Jan Kiszka > > It is not safe to retrieve the KVM internal state of a given cpu > while its potentially modifying it. > > Queue the request to run on cpu context, similarly to qemu-kvm. > Even better is to query the state in the cpu thread; but that can come later. -- error compiling committee.c: too many arguments to function