All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: "Raj, Ashok" <ashok.raj@intel.com>
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 14:28:00 +0100	[thread overview]
Message-ID: <20180217132800.GA10565@pd.tnic> (raw)
In-Reply-To: <20180217130753.GA25024@araj-mobl1.jf.intel.com>

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.

So no need to do anything now.

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-16 11:26 [PATCH 0/3] x86/microcode: " 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 [this message]
2018-02-17 17:06       ` Raj, Ashok
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=20180217132800.GA10565@pd.tnic \
    --to=bp@alien8.de \
    --cc=ashok.raj@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=x86@kernel.org \
    --subject='Re: [PATCH 2/3] x86/CPU: Add a microcode loader callback' \
    /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

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.