linux-kernel - Re: [PATCH] x86_64: Move cpu long mode verification code to common file (was Re: [RFC] [PATCH 10/16] x86

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: <20061115225429.GD3722@elf.ucw.cz>
Date:	Wed, 15 Nov 2006 23:54:29 +0100
From:	Pavel Machek <pavel@...e.cz>
To:	Vivek Goyal <vgoyal@...ibm.com>
Cc:	Andi Kleen <ak@...e.de>,
	linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Reloc Kernel List <fastboot@...ts.osdl.org>,
	ebiederm@...ssion.com, akpm@...l.org, hpa@...or.com,
	magnus.damm@...il.com, lwang@...hat.com, dzickus@...hat.com,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: [PATCH] x86_64: Move cpu long mode verification code to common file (was Re: [RFC] [PATCH 10/16] x86_64: 64bit PIC ACPI wakeup)

Hi!

> > It would be much better if this least this CPUID code was in a common shared 
> > file with head.S

> 
> Pleaese find attached the patch which moves verify_cpu code to a
> single file arch/x86_64/kernel/verify_cpu.S and this file is included
> by all to do the cpu long mode and SSE checks.

Looks ok to me on quick look...

> @@ -0,0 +1,103 @@
> +/*
> + *
> + *	verify_cpu.S
> + *
> + * 	14 Nov 2006  Vivek Goyal: Created the file

Could we get copyright/GPL here, instead?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/