[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160219104642.GB8918@pd.tnic>
Date: Fri, 19 Feb 2016 11:46:42 +0100
From: Borislav Petkov <bp@...en8.de>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Boris Ostrovsky <boris.ostrovsky@...cle.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
david.vrabel@...rix.com,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
xen-devel@...ts.xenproject.org
Subject: Re: [PATCH] x86, microcode: Remove unnecessary paravirt_enabled check
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 <boris.ostrovsky@...cle.com>
> 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.
Powered by blists - more mailing lists