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:	Fri, 23 May 2008 15:15:07 +0200
From:	Pavel Machek <pavel@....cz>
To:	Dave Jones <davej@...hat.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>, hpa@...or.com
Subject: Re: [X86] Move the 64-bit Intel specific parts out of setup_64.c

Hi!

> Create a separate intel_64.c file in the cpu/ dir for
> the useful parts to live in.
> 
> Signed-off-by: Dave Jones <davej@...hat.com>

> +/*
> + * find out the number of processor cores on the die
> + */
> +static int __cpuinit intel_num_cpu_cores(struct cpuinfo_x86 *c)
> +{
> +	unsigned int eax, t;
> +
> +	if (c->cpuid_level < 4)
> +		return 1;
> +
> +	cpuid_count(4, 0, &eax, &t, &t, &t);
> +
> +	if (eax & 0x1f)
> +		return ((eax >> 26) + 1);
> +	else
> +		return 1;
> +}

I don't get it. Original Core duo is not 64 bit capable... so this
should go into common code?
-- 
(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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ