linux-kernel - Re: x86 merge: Keep kernel/cpu for CPU specific code?

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]

Message-ID: <20071113141434.GI18993@erda.amd.com>
Date:	Tue, 13 Nov 2007 15:14:34 +0100
From:	"Robert Richter" <robert.richter@....com>
To:	"Adrian Bunk" <bunk@...nel.org>
cc:	"Thomas Gleixner" <tglx@...utronix.de>,
	"Ingo Molnar" <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
	"Andi Kleen" <andi@...stfloor.org>,
	"LKML" <linux-kernel@...r.kernel.org>
Subject: Re: x86 merge: Keep kernel/cpu for CPU specific code?

On 13.11.07 13:02:08, Adrian Bunk wrote:
> On Tue, Nov 13, 2007 at 12:44:43PM +0100, Robert Richter wrote:
> > x86 CPU specific code is currently implemented in different ways for
> > 64 and 32 bit. While there are almost no CPU specific files for 64
> > bit, there is the arch/x86/kernel/cpu/ directory for 32 bit. Is there
> > already an idea about whether to use kernel/cpu also for 64 bit?
> 
> It is also used for 64bit for years.

Yes, but almost all files in arch/x86/kernel/cpu/ depend on
CONFIG_X86_32.

Here is an example for similiar implementations:

arch/x86/kernel/cpu/amd.c:static void __cpuinit init_amd(struct cpuinfo_x86 *c)
arch/x86/kernel/setup_64.c:static void __cpuinit init_amd(struct cpuinfo_x86 *c)

The question is, will there be a CPU specific file such as amd.c?

-Robert

-- 
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@....com


-
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/