From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linutronix.de (193.142.43.55:993) by crypto-ml.lab.linutronix.de with IMAP4-SSL for ; 02 Nov 2019 07:36:33 -0000 Received: from us-smtp-2.mimecast.com ([205.139.110.61] helo=us-smtp-delivery-1.mimecast.com) by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1iQnxX-0001jO-9f for speck@linutronix.de; Sat, 02 Nov 2019 08:36:32 +0100 Received: by mail-wr1-f70.google.com with SMTP id a15so6982046wrr.0 for ; Sat, 02 Nov 2019 00:36:20 -0700 (PDT) Received: from [192.168.42.104] (mob-109-112-8-141.net.vodafone.it. [109.112.8.141]) by smtp.gmail.com with ESMTPSA id p12sm11224491wrm.62.2019.11.02.00.36.18 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 02 Nov 2019 00:36:18 -0700 (PDT) Subject: [MODERATED] Re: [PATCH v8 3/5] NX 3 References: <1572564827-26288-1-git-send-email-pbonzini@redhat.com> <1572564827-26288-4-git-send-email-pbonzini@redhat.com> <20191101002350.GA26083@guptapadev.amr> <91ff125b-068d-9f4a-fa3c-ca0bfec38c17@redhat.com> <20191101183815.GA6582@u1904> <20191101185126.GA12673@elm> <20191101203633.GA9829@u1904> From: Paolo Bonzini Message-ID: Date: Sat, 2 Nov 2019 08:36:15 +0100 MIME-Version: 1.0 In-Reply-To: <20191101203633.GA9829@u1904> Content-Type: multipart/mixed; boundary="IhMal9z0nWyhveExB2n4sfUMUsiUTaGe6"; protected-headers="v1" To: speck@linutronix.de List-ID: This is an OpenPGP/MIME encrypted message (RFC 4880 and 3156) --IhMal9z0nWyhveExB2n4sfUMUsiUTaGe6 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 01/11/19 21:36, speck for mark gross wrote: >>> We (I) have attempted the backports of this and quicly hit issues wit= h the page >>> zapping changes do to code flux in the upstream. My troubles started= with with >>> 5.2 and 4.19.=20 >> >> Is this due to the lack of kvm_mmu_zap_all_fast()? I believe that Paol= o >> and others said in an older thread that >> kvm_mmu_invalidate_zap_all_pages() could be used instead. >> >> That's what I've been planning to do in Ubuntu but I haven't had a >> chance to test it yet. > > I missed that comment. I'll retry my backporting using your recomendat= ion > above. Correct, backports were discussed a couple weeks ago and nothing has changed since then. Paolo --IhMal9z0nWyhveExB2n4sfUMUsiUTaGe6--