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: <52F15000.2080102@zytor.com>
Date:	Tue, 04 Feb 2014 12:39:28 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	"Theodore Ts'o" <tytso@....edu>,
	Stephan Mueller <smueller@...onox.de>,
	Jörn Engel <joern@...fs.org>,
	Linux Kernel Developers List <linux-kernel@...r.kernel.org>,
	"Maciej W. Rozycki" <macro@...ux-mips.org>,
	Ralf Baechle <ralf@...ux-mips.org>, dave.taht@...il.com,
	John Crispin <blogic@...nwrt.org>, andrewmcgr@...il.com,
	Thorsten Glaser <tg@...bsd.de>, sandyinchina@...il.com
Subject: Re: [RFC PATCH 0/5] CPU Jitter RNG

On 02/04/2014 11:39 AM, Geert Uytterhoeven wrote:
> On Tue, Feb 4, 2014 at 8:23 PM,  <tytso@....edu> wrote:
>> However, where a decade ago the ethernet card probably had its own
>> independent clock crystal/oscillator, I'm going to guess that these
>> days with SOC's and even on laptops, with ethernet device part of the
>> chipset, it is probably being driven off the same master oscillator.
> 
> USB typically still has its own crystal.

USB and the Ethernet PHY frequently do still have their own crystals,
for reasons not entirely clear to me.  However, what all of these have
in common is that they are way out in the periphery.

>> I wonder if there's anyway we can either figure out manually, or
>> preferably, automatically at boot time, which devices actually have
>> independent clock oscillators.
> 
> You may find this information in the DT on some platforms (if you're
> lucky).

On most systems today, all the high speed clocks (CPU, memory, etc.) are
all fed from a single oscillator.  On PCs there used to be a separate
14.31818 MHz oscillator for the PIT, PMTIMER and HPET, but that is
increasingly handled by a frequency converter from the main bus clock.
Oscillators are expensive, and true asynchronous domains cause problems
with metastability.

	-hpa



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