Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp606568ybp; Wed, 9 Oct 2019 01:03:27 -0700 (PDT) X-Google-Smtp-Source: APXvYqwXf2XLOlRkFtpAKmozrSLFZAId2X+MRbS8dxfXzakyTl+wTrjuNacYvPLmkhBXl29G/CvZ X-Received: by 2002:aa7:ce94:: with SMTP id y20mr1723545edv.189.1570608206946; Wed, 09 Oct 2019 01:03:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1570608206; cv=none; d=google.com; s=arc-20160816; b=oi05pGH1dTpbHOIUgAxEa9FY6Xv6GU4vnYZ7QNRDW5k6qymlgGEeE1HBkPg6Fzdzyn nn90olte5aV3/LaJfuhGUvhNzIx2Nkb3Ftps648+VlZMQJLYP487g6RX+m+ynLelpac3 XaeDRe5bstA4cJhN931CP5YuTn2r1fwgygWXah+CmOSo4Qm8HgPtmnpZo5m/H9cduJ22 2Dgsh9hqCFiT3ScJ2xd2zeZjfRUmew5CXnJN+HDXpHEy6OtzV/UhvwyBrgPcqNGgNWRi p02xc+SjefAJMZJu8FGy65F9HIUXXpmL96IG3Btlb2Y5kTpntSpIQpKBZcjAbgwlghI8 p/AQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=vwdRHZu7LyE+1Szl+0xVWJbgMHwHD1BsmK+d5dOSKbo=; b=JdykjmNmpwbwl6px1ootRTmnD8iV+xNXy5emLKUv/m+Av7sgWSqjp/luSrq4lqy7lA xO5SU5iAF/K7b6RDf5TGD3z81+xiG8Y4CsQnxzzdfFNJuq0+PH0adddr5wWc3k4doy7J 6jAwvvFv+Cx4+KE6737598Y73QGd3rWZRIHltGyBBzFE8wOtjBDlocOIOiOCm+graMWO KgvKX72BFb9hZl49rzHXbrUd/SfECo/j0F9TOUiL8Jv79jtqzuqiyVEvqNOs4uPgtby1 LHCxeopajYb8n9jlVr2D9ottDQxv8AMFO+l4Wt+JMU51lz7W71PN5vcXTocVeo9KRmps au7A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m21si878691edc.153.2019.10.09.01.03.02; Wed, 09 Oct 2019 01:03:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726068AbfJIICo (ORCPT + 99 others); Wed, 9 Oct 2019 04:02:44 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:43187 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725440AbfJIICn (ORCPT ); Wed, 9 Oct 2019 04:02:43 -0400 Received: by atrey.karlin.mff.cuni.cz (Postfix, from userid 512) id 66B758032F; Wed, 9 Oct 2019 10:02:26 +0200 (CEST) Date: Wed, 9 Oct 2019 10:02:40 +0200 From: Pavel Machek To: David Laight Cc: "Theodore Y. Ts'o" , Linus Torvalds , Thomas Gleixner , "Ahmed S. Darwish" , LKML , Nicholas Mc Guire , the arch/x86 maintainers , Andy Lutomirski , Kees Cook Subject: Re: x86/random: Speculation to the rescue Message-ID: <20191009080240.GA11561@amd> References: <20191006114129.GD24605@amd> <20191006173501.GA31243@amd> <20191006182103.GA2394@amd> <20191007114734.GA6104@mit.edu> <20191007221817.GA4027@amd> <4748b43e6b00415fb21c1a127a835e87@AcuMS.aculab.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: <4748b43e6b00415fb21c1a127a835e87@AcuMS.aculab.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! > > I have many systems including SoC here, but technology needed for NAND > > flash is different from technology for CPU, so these parts do _not_ > > share a silicon die. They do not even share same package. (Also RTC > > tends to be on separate chip, connected using i2c). >=20 > NAND flash requires ECC so is likely to be async. > But I2C is clocked from the cpu end - so is fixed. RTC i2c may be clocked from the CPU end, but the time source needs to work when machine is off, so that has a separate crystal for timekeeping. > Also an embedded system could be booting off a large serial EEPROM. > These have fixed timings and are clocked from the cpu end. Have you seen such system running Linux? Best regards, Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blo= g.html --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAl2dlCAACgkQMOfwapXb+vKhEwCeOJiJPIsQBqYclwYrDh8xUdYO 9+cAoI0TgFDfubmPNTzSK/Ib7YMBoqtr =SfmC -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62--