From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jes Sorensen Subject: Re: [patch] fold struct vcpu_info into CPUState Date: Mon, 27 Oct 2008 10:48:16 +0100 Message-ID: <49058E60.6080507@sgi.com> References: <48E0F318.7050303@sgi.com> <5d6222a80810131524s7ec55bfyb296085c6c2ac4af@mail.gmail.com> <48F8AF00.1050304@sgi.com> <5d6222a80810171427m252a1cf9he711ab247ae84530@mail.gmail.com> <4901F083.3070006@sgi.com> <1224875457.9634.63.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Glauber Costa , kvm@vger.kernel.org, kvm-ia64@vger.kernel.org To: Hollis Blanchard Return-path: Received: from relay1.sgi.com ([192.48.171.29]:44824 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1750983AbYJ0JsT (ORCPT ); Mon, 27 Oct 2008 05:48:19 -0400 In-Reply-To: <1224875457.9634.63.camel@localhost.localdomain> Sender: kvm-owner@vger.kernel.org List-ID: Hollis Blanchard wrote: > It looks like qemu is actually switching threads when this happens... > I'm not sure what the current state is of qemu/KVM threads... I think we > have 1 thread per vcpu, plus 1 IO thread? If that's right, maybe > current_env isn't being initialized in the IO thread; I only see that > happening inside ap_main_loop(), which is the vcpu thread. > Hmmm, this is bizarre. If it was the IO thread dieing because of this I would expect the same to happen on ia64. Could you try and add a test in the code to find out which thread you are when you die, and maybe check for current_env being valid? Thanks, Jes