From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx3-rdu2.redhat.com ([66.187.233.73] helo=mx1.redhat.com) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fNwzT-0008N9-1f for speck@linutronix.de; Wed, 30 May 2018 11:01:55 +0200 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 30E22859A2 for ; Wed, 30 May 2018 09:01:48 +0000 (UTC) Received: from [10.36.118.56] (unknown [10.36.118.56]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A55DA111765A for ; Wed, 30 May 2018 09:01:47 +0000 (UTC) Subject: [MODERATED] Re: [PATCH 1/2] L1TF KVM 1 References: <20180529194214.2600-1-pbonzini@redhat.com> <20180529194240.7F1336110A@crypto-ml.lab.linutronix.de> From: Paolo Bonzini Message-ID: <99e589e5-6385-2e3e-aac4-6a5d6955a505@redhat.com> Date: Wed, 30 May 2018 11:01:45 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="FrPYZ8VV0D9uHe1kXlXFfYKToW2C6AsEF"; protected-headers="v1" To: speck@linutronix.de List-ID: This is an OpenPGP/MIME encrypted message (RFC 4880 and 3156) --FrPYZ8VV0D9uHe1kXlXFfYKToW2C6AsEF Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 30/05/2018 01:54, speck for Andrew Cooper wrote: > Other bits I don't understand are the 64k limit in the first place, why= > it gets walked over in 4k strides to begin with (I'm not aware of any > prefetching which would benefit that...) and why a particularly > obfuscated piece of magic is used for the 64byte strides. That is the only part I understood, :) the 4k strides ensure that the source data is in the TLB. Why that is needed is still a mystery though.= Paolo --FrPYZ8VV0D9uHe1kXlXFfYKToW2C6AsEF--