Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754585AbYLBU6v (ORCPT ); Tue, 2 Dec 2008 15:58:51 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754407AbYLBU6j (ORCPT ); Tue, 2 Dec 2008 15:58:39 -0500 Received: from mx2.redhat.com ([66.187.237.31]:50980 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754387AbYLBU6h (ORCPT ); Tue, 2 Dec 2008 15:58:37 -0500 Message-ID: <4935A0FF.7070105@redhat.com> Date: Tue, 02 Dec 2008 22:56:31 +0200 From: Avi Kivity User-Agent: Thunderbird 2.0.0.18 (X11/20081119) MIME-Version: 1.0 To: Steven Rostedt CC: Luis Henriques , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Steven Rostedt , Ingo Molnar Subject: Re: [BUG] kvm crashes in 2.6.28-rc6-00007-ged31348 References: <20081130193401.GA7690@hades> <4932F59D.2060002@redhat.com> <20081130203833.GA14903@hades> <4932FB47.6090300@redhat.com> <20081130210406.GA17952@hades> <493528D8.8010904@redhat.com> <20081202190914.GA12115@hades> <20081202194610.GA4864@hades> <1228249509.4886.11.camel@localhost.localdomain> <49359CDF.5060300@redhat.com> <1228250921.4886.14.camel@localhost.localdomain> In-Reply-To: <1228250921.4886.14.camel@localhost.localdomain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1132 Lines: 30 Steven Rostedt wrote: >> In arch/x86/kvm/svm.c, function svm_vcpu_run(), everything between the >> vmrun instruction and the call to load_host_msrs() is executed without a >> live pda, so no smp_processor_id(). Could easily be fixed by >> rearranging things. >> > > That would be best, but if you have trouble, you could surround the > trouble area with a: tracing_stop(); tracing_start(); That will prevent > tracing within those locations. The function tracer will still be > called, but it will exit the function without doing anything else. > > Note: that stops tracing on all CPUS, not just the CPU that called it. > The vmrun instruction can execute for a long time (hours, if you have a dyntick kernel and no timers scheduled), so that's less than optimal. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/