From: Borislav Petkov <bp@alien8.de>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, linux-kernel@vger.kernel.org,
david.vrabel@citrix.com, konrad.wilk@oracle.com,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] x86, microcode: Remove unnecessary paravirt_enabled check
Date: Thu, 11 Feb 2016 19:17:49 +0100 [thread overview]
Message-ID: <20160211181749.GF5565@pd.tnic> (raw)
In-Reply-To: <1455203598-14378-1-git-send-email-boris.ostrovsky@oracle.com>
On Thu, Feb 11, 2016 at 10:13:18AM -0500, Boris Ostrovsky wrote:
> Commit a18a0f6850d4 ("x86, microcode: Don't initialize microcode code on
> paravirt") added a paravirt test in microcode_init(), primarily to avoid
> making mc_bp_resume()->load_ucode_ap()->check_loader_disabled_ap() calls
> On 32-bit kernels this callchain ends up using __pa_nodebug() macro
> which is invalid for Xen PV guests.
>
> A subsequent commit, fbae4ba8c4a3 ("x86, microcode: Reload microcode on
> resume"), eliminated this callchain thus making a18a0f6850d4
> unnecessary.
>
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> ---
> arch/x86/kernel/cpu/microcode/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied, thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-02-11 18:17 UTC|newest]
Thread overview: 22+ 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-11 18:17 ` Borislav Petkov [this message]
2016-02-19 10:06 ` Andy Shevchenko
2016-02-19 10:06 ` Andy Shevchenko
2016-02-19 10:18 ` Borislav Petkov
2016-02-19 10:18 ` Borislav Petkov
2016-02-19 10:33 ` Andy Shevchenko
2016-02-19 10:46 ` Borislav Petkov
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:21 ` Andy Shevchenko
2016-02-19 11:36 ` Borislav Petkov
2016-02-19 11:36 ` Borislav Petkov
2016-02-19 11:10 ` Borislav Petkov
2016-02-19 11:00 ` Andy Shevchenko
2016-02-19 10:50 ` Andy Shevchenko
2016-02-19 10:46 ` Borislav Petkov
2016-02-19 10:33 ` Andy Shevchenko
-- strict thread matches above, loose matches on Subject: below --
2016-02-11 15:13 Boris Ostrovsky
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=20160211181749.GF5565@pd.tnic \
--to=bp@alien8.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.