From: Borislav Petkov <bp@alien8.de>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
david.vrabel@citrix.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] x86, microcode: Remove unnecessary paravirt_enabled check
Date: Fri, 19 Feb 2016 11:46:42 +0100 [thread overview]
Message-ID: <20160219104642.GB8918@pd.tnic> (raw)
In-Reply-To: <CAHp75VdBcqPnijnY170eU15Q9bXGXmSiBNKxbLoeSMUo9hC6Vg@mail.gmail.com>
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@oracle.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.
next prev parent reply other threads:[~2016-02-19 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 15:13 [PATCH] x86, microcode: Remove unnecessary paravirt_enabled check Boris Ostrovsky
2016-02-11 18:17 ` Borislav Petkov
2016-02-19 10:06 ` Andy Shevchenko
2016-02-19 10:18 ` Borislav Petkov
2016-02-19 10:33 ` Andy Shevchenko
2016-02-19 10:46 ` Borislav Petkov [this message]
2016-02-19 10:50 ` Andy Shevchenko
2016-02-19 11:00 ` Andy Shevchenko
2016-02-19 11:10 ` Borislav Petkov
2016-02-19 11:21 ` Andy Shevchenko
2016-02-19 11:36 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160219104642.GB8918@pd.tnic \
--to=bp@alien8.de \
--cc=andy.shevchenko@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).