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] [day] [month] [year] [list]
Message-ID: <20070212235907.GC13573@redhat.com>
Date:	Mon, 12 Feb 2007 18:59:07 -0500
From:	Dave Jones <davej@...hat.com>
To:	Simon Arlott <6bc04bda904655a1b91hgkso0000m4ev@...nder.lp0.eu>
Cc:	Kyle McMartin <kyle@...artin.ca>, Mark de Vries <mark@...hyx.net>,
	linux-kernel@...r.kernel.org
Subject: Re: Which CPU for VIA C7/Esther?

On Mon, Feb 12, 2007 at 11:46:46PM +0000, Simon Arlott wrote:

 > MVIAC3_2 doesn't enable X86_GOOD_APIC

which is pretty irrelevant unless you have a dual C7.

 > , try M686 (Pentium-Pro) - but that won't enable MMX and SSE (via -march=c3-2).

If gcc generated SSE/MMX instructions that would be a bug. (hint: it doesn't).

 > These CPUs support SSE2 too... 

The SSE/SSE2/SSE3 etc support for userspace is unconditional. The context switch paths will
save/restore the registers regardless of the CPU you've compiled your kernel for.
The only SSE code in the kernel is the memcpy code (which wasn't that big a win when
I last tried it on VIA due to their poor memory bandwidth), and the RAID code, which
gets tested at runtime rather than compile time.

 > Also, for the C7 you'll want CRYPTO_DEV_PADLOCK_* (Hardware Crypto Devices, Support for VIA PadLock ACE) and HW_RANDOM_VIA (VIA HW Random Number Generator support).

Yes. But these aren't dependant on any CPU config options.

		Dave

-- 
http://www.codemonkey.org.uk
-
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