From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 1/2] don't start cpu main loop while there is still init work to do. Date: Mon, 04 May 2009 17:33:26 +0300 Message-ID: <49FEFCB6.5070906@redhat.com> References: <1241037101-24842-1-git-send-email-glommer@redhat.com> <1241037101-24842-2-git-send-email-glommer@redhat.com> <49FEA7C2.7050908@redhat.com> <20090504142627.GG12844@poweredge.glommer> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, ehabkost@redhat.com To: Glauber Costa Return-path: Received: from mx2.redhat.com ([66.187.237.31]:48078 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753692AbZEDOeA (ORCPT ); Mon, 4 May 2009 10:34:00 -0400 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n44EY1Q2012431 for ; Mon, 4 May 2009 10:34:01 -0400 In-Reply-To: <20090504142627.GG12844@poweredge.glommer> Sender: kvm-owner@vger.kernel.org List-ID: Glauber Costa wrote: >> I'd like to avoid vcpu ioctls from more than one thread, in case we ever >> move to a syscall implementation. >> > > Although I don't see exactly what's your point in here. > We're just adding a serialization points through pthreads function, not doing any ioctl from > the outside. > Doesn't the lapic creation call KVM_CREATE_LAPIC? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.