Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756119AbaDHC5p (ORCPT ); Mon, 7 Apr 2014 22:57:45 -0400 Received: from mga09.intel.com ([134.134.136.24]:31886 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754690AbaDHC5o (ORCPT ); Mon, 7 Apr 2014 22:57:44 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.97,815,1389772800"; d="scan'208";a="516603127" Date: Tue, 8 Apr 2014 10:53:29 +0800 From: Fengguang Wu To: "Romer, Benjamin M" Cc: *S-Par-Maintainer , Ken Cox , Greg Kroah-Hartman , "linux-kernel@vger.kernel.org" , "devel@driverdev.osuosl.org" , Jet Chen Subject: Re: [visorchipset] invalid opcode: 0000 [#1] PREEMPT SMP Message-ID: <20140408025329.GB16434@localhost> References: <20140407111725.GC25152@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Benjamin, > Fengguang, > > I ran your script against freshly-checked-out source from staging-next, and was not able to reproduce the error with it. My boot log is attached. I noticed that your log did not have "Hypervisor detected: KVM" in the trace. The KVM options in your script also differ substantially from the ones shown at the end of your trace... > When I reran your script with the "-cpu Haswell,+smep,+smap" option I was able to get the same result as you. IMHO KVM should not be setting this bit if it's emulating bare metal. Sorry.. We tried to provide a simplified reproduce script and in your case, it has a significant mismatch with the real KVM options. We'll fix it, thanks for pointing it out! Thanks, Fengguang -- 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/