From: Randy Dunlap <rdunlap@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>
Subject: Re: linux-next: Tree for May 18 (arch/x86/kernel/cpu/microcode/intel.o)
Date: Wed, 18 May 2022 14:54:45 -0700 [thread overview]
Message-ID: <df5ed1d0-6304-89b8-ad68-0cf6a59d8614@infradead.org> (raw)
In-Reply-To: <YoVlwN/IeVXoMaq1@zn.tnic>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
On 5/18/22 14:34, Borislav Petkov wrote:
> On Wed, May 18, 2022 at 02:05:28PM -0700, Randy Dunlap wrote:
>> on x86_64:
>>
>> CONFIG_PROCESSOR_SELECT=y
>> # CONFIG_CPU_SUP_INTEL is not set <<<<<
>> CONFIG_CPU_SUP_AMD=y
>> # CONFIG_CPU_SUP_HYGON is not set
>> CONFIG_CPU_SUP_CENTAUR=y
>> CONFIG_CPU_SUP_ZHAOXIN=y
>>
>> CONFIG_MICROCODE=y
>> CONFIG_MICROCODE_INTEL=y <<<<<
>> CONFIG_MICROCODE_AMD=y
>
> Hmm:
>
> $ grep -E "(PROCESSOR_SELECT|CPU_SUP|MICROCODE)" .config
> CONFIG_PROCESSOR_SELECT=y
> # CONFIG_CPU_SUP_INTEL is not set
> CONFIG_CPU_SUP_AMD=y
> # CONFIG_CPU_SUP_HYGON is not set
> CONFIG_CPU_SUP_CENTAUR=y
> CONFIG_CPU_SUP_ZHAOXIN=y
> CONFIG_MICROCODE=y
> CONFIG_MICROCODE_INTEL=y
> CONFIG_MICROCODE_AMD=y
> CONFIG_MICROCODE_OLD_INTERFACE=y
>
> that builds fine here on tip/master. Or is it linux-next specific? I'd
> hope not.
>
> Can you send me your whole .config pls and how exactly you reproduce it,
> i.e., on which tree?
This is linux-next-20220518. config file is attached.
cp the config file to blddir/.config
make ARCH=x86_64 O=blddir oldconfig
make ARCH=x86_64 O=blddir -j9 all
--
~Randy
[-- Attachment #2: config-r2878.gz --]
[-- Type: application/gzip, Size: 34373 bytes --]
next prev parent reply other threads:[~2022-05-18 22:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 10:29 linux-next: Tree for May 18 Stephen Rothwell
2022-05-18 21:05 ` linux-next: Tree for May 18 (arch/x86/kernel/cpu/microcode/intel.o) Randy Dunlap
2022-05-18 21:34 ` Borislav Petkov
2022-05-18 21:54 ` Randy Dunlap [this message]
2022-05-18 22:29 ` Borislav Petkov
2022-05-18 22:40 ` Randy Dunlap
2022-05-19 14:55 ` Borislav Petkov
2022-05-19 14:57 ` [PATCH] platform/x86/intel/ifs: Add CPU_SUP_INTEL dependency Borislav Petkov
2022-05-19 17:47 ` Hans de Goede
2022-05-19 15:03 ` [PATCH] x86/microcode: Add explicit CPU vendor dependency 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=df5ed1d0-6304-89b8-ad68-0cf6a59d8614@infradead.org \
--to=rdunlap@infradead.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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 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).