From: "H. Peter Anvin" <hpa@zytor.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
Aravind.Gopalakrishnan@amd.com, tglx@linutronix.de, bp@suse.de,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/microcode] x86, microcode: Move to a proper location
Date: Tue, 14 Jan 2014 11:18:57 -0800 [thread overview]
Message-ID: <52D58DA1.2070400@zytor.com> (raw)
In-Reply-To: <20140114185802.GB29871@pd.tnic>
On 01/14/2014 10:58 AM, Borislav Petkov wrote:
> On Tue, Jan 14, 2014 at 08:10:28AM -0800, H. Peter Anvin wrote:
>> Quite frankly I would be much happier if we didn't stash so much under
>> arch/x86/kernel/cpu ... quite frankly it feels like almost *anything*
>> could go under there. The microcode code, for example, could go under
>> its own subtree.
>
> Yeah, about the microcode, shouldn't it be under kernel/cpu/? My train
> of thought is: because it is cpu-related functionality, it logically
> belongs there.
arch/x86/cpu/microcode seems clean. I'm wondering if what is mostly
currently in arch/x86/kernel/cpu should be mostly in something like
arch/x86/cpu/init.
-hpa
next prev parent reply other threads:[~2014-01-14 19:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-bad5fa631fca5466401cd4a48e30cc1f1cb6101e@git.kernel.org>
2014-01-14 16:10 ` [tip:x86/microcode] x86, microcode: Move to a proper location H. Peter Anvin
2014-01-14 16:22 ` Ingo Molnar
2014-01-14 16:36 ` Borislav Petkov
2014-01-14 16:39 ` H. Peter Anvin
2014-01-14 17:38 ` Ingo Molnar
2014-01-14 18:58 ` Borislav Petkov
2014-01-14 19:18 ` H. Peter Anvin [this message]
2014-01-14 19:27 ` Borislav Petkov
2014-01-14 19:32 ` H. Peter Anvin
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=52D58DA1.2070400@zytor.com \
--to=hpa@zytor.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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