All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Raj, Ashok" <ashok.raj@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH 2/3] x86/CPU: Add a microcode loader callback
Date: Sat, 17 Feb 2018 09:06:43 -0800	[thread overview]
Message-ID: <20180217170642.GA27868@araj-mobl1.jf.intel.com> (raw)
In-Reply-To: <20180217132800.GA10565@pd.tnic>

On Sat, Feb 17, 2018 at 02:28:00PM +0100, Borislav Petkov wrote:
> On Sat, Feb 17, 2018 at 05:07:53AM -0800, Raj, Ashok wrote:
> > Could you only list it there instead? common.c has no other
> > microcode related functions other than this.?
> 
> I already explained that to you: this function is called by the loader
> but it uses facilities which are closer to cpu/common.c - get_cpu_cap(),
> etc.
> 
> Also, this file will be split eventually after the CPUID cleanup.
> 
> So it could just as well be called recheck_cpu_caps(), without the
> "microcode" prefix.

Never mind.. now that rings a bell :-)

> 
> So no need to do anything now.
> 

  reply	other threads:[~2018-02-17 17:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 11:26 [PATCH 0/3] x86/microcode: Add a microcode loader callback Borislav Petkov
2018-02-16 11:26 ` [PATCH 1/3] x86/microcode: Propagate return value from updating functions Borislav Petkov
2018-02-17 10:12   ` [tip:x86/pti] " tip-bot for Borislav Petkov
2018-02-16 11:26 ` [PATCH 2/3] x86/CPU: Add a microcode loader callback Borislav Petkov
2018-02-17 10:12   ` [tip:x86/pti] " tip-bot for Borislav Petkov
2018-02-17 13:07   ` [PATCH 2/3] " Raj, Ashok
2018-02-17 13:28     ` Borislav Petkov
2018-02-17 17:06       ` Raj, Ashok [this message]
2018-02-16 11:26 ` [PATCH 3/3] x86/CPU: Check CPU feature bits after microcode upgrade Borislav Petkov
2018-02-17 10:13   ` [tip:x86/pti] " tip-bot for 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=20180217170642.GA27868@araj-mobl1.jf.intel.com \
    --to=ashok.raj@intel.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=x86@kernel.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.