linux-kernel - Re: [tip:x86/microcode] x86, microcode: Move to a proper location

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 14 Jan 2014 18:38:27 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Borislav Petkov <bp@...en8.de>, linux-kernel@...r.kernel.org,
	Aravind.Gopalakrishnan@....com, tglx@...utronix.de, bp@...e.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/microcode] x86, microcode: Move to a proper location


* H. Peter Anvin <hpa@...or.com> wrote:

> On 01/14/2014 08:36 AM, Borislav Petkov wrote:
> > On Tue, Jan 14, 2014 at 05:22:03PM +0100, Ingo Molnar wrote:
> >> Absolutely. I think moving arch/x86/kernel/cpu/ to arch/x86/cpu/
> >> would be a first good step. It's all kernel code, there's other
> >> subdirectories there that are kernel code ('pci/', 'platform/', etc.),
> >> so there's little point in continuing the historic accident of a
> >> 'kernel/' subdirectory.
> >>
> >> Once that is done we can move certain things outside as well - for
> >> example arch/x86/cpu/perf/ could probably move to arch/x86/events/,
> >> because that code is not about CPU events anymore either.
> > 
> > All fine and dandy with me, but I'd prefer to do this after the merge
> > window, i.e. for 3.15. Rushing it now would just cause unnecessary
> > trouble IMO.
> > 
> 
> Oh, absolutely.

Agreed.

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/