From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2992817AbcBSKqt (ORCPT ); Fri, 19 Feb 2016 05:46:49 -0500 Received: from mail.skyhub.de ([78.46.96.112]:37288 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751021AbcBSKqq (ORCPT ); Fri, 19 Feb 2016 05:46:46 -0500 Date: Fri, 19 Feb 2016 11:46:42 +0100 From: Borislav Petkov To: Andy Shevchenko Cc: Boris Ostrovsky , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , david.vrabel@citrix.com, Konrad Rzeszutek Wilk , xen-devel@lists.xenproject.org Subject: Re: [PATCH] x86, microcode: Remove unnecessary paravirt_enabled check Message-ID: <20160219104642.GB8918@pd.tnic> References: <1455203598-14378-1-git-send-email-boris.ostrovsky@oracle.com> <20160219101822.GA8918@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 19, 2016 at 12:33:46PM +0200, Andy Shevchenko wrote: > No, the commit 84aba677f009 as of today's linux-next on which I commented. You commented under the "> A subsequent commit, fbae4ba8c4a3" which confused me as to which commit is the culprit. > commit 84aba677f009e20185aea322563389ad56e0ef7e > Author: Boris Ostrovsky > Date: Tue Feb 16 09:43:19 2016 +0100 > > x86/microcode: Remove unnecessary paravirt_enabled check > > One more thing: I run this kernel as a second from kexec. It might be > related as well. For now I have no possibility to run it as a first > kernel. Well, how exactly are you triggering this? Do you have a splat or some other register dump so that I can try to pinpoint this. I'll need more info so that I can reproduce it here and debug it. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply.