Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp921577ima; Fri, 1 Feb 2019 13:09:51 -0800 (PST) X-Google-Smtp-Source: ALg8bN7V1HwCSYo8NeN0RO+TE0VkJj2GHMy5MakepCYw2dw+G9NyjXSlRcGLF64adrEUx9a1VwEp X-Received: by 2002:a62:9fd9:: with SMTP id v86mr40706477pfk.191.1549055391073; Fri, 01 Feb 2019 13:09:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549055391; cv=none; d=google.com; s=arc-20160816; b=lU5t/wrHQyfXbteqORPt3NLJPI8u06tfIQeWnmduVqEdf7E/3rnv8mBnGDM6HM66lw soE6LwbZ5jMk5wpmDcn9sLRxthYUIzUmXQ3XeRP6Hjzmq2JxP9GuWuVlWMILGhTv2x/s t/405hvBddeLfhgcCYZYmy3254MJ+NHhDZyivfSXXjXonGlQVx2onI6h5q9dhBzkczUc HV6FbmHX8bkhQUp/R7RhORLFXExgseA+HGgfuJ+zz0kD91EorOr7FjhxQj06O/XXrTkV Nfi4yOBQ0Fu+gAZKbYQR5LJcUDvErEGdjM+YAJdumQ8n1HrWVHvabNqrfdUxDsSrAf6H ldOA== 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=gHsXDjL9X/1Jo4FWZRLueeQ9s8tedCa/nQhpTsJjl5o=; b=nNg3wHTHuZaQ0F7VzBM/ONOax9IFMGpMxCazPKogIgePWYbxoSlN5mK0ecRhy9WOBH Pkv0sr6xF+GHWRyumvd1SG5NP3kG9o4vJ1wx++B+OeXzyrvyFoqisxwjqBV9AYRv5Z3n 2HXgP/FsYmwjiJduGnAb3k4O8CdatqSX2lBgVgZCv94E7UigjzvBRcHdPXJOXW5iu84+ 5U/6n7NUW1Pg9Ysa03687gaS5/ycgyvYPdJMvivOnMh/Tq/UbrT7/kJB6bmy5xKxm/ZU uMW/NdCUwSBJnBreIfgnFPCARS2rLoJRfzVg+nksoRI14ShfHnCJGEjeIu1hR98UR2ia jYow== 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 n184si3914371pgn.95.2019.02.01.13.09.32; Fri, 01 Feb 2019 13:09:51 -0800 (PST) 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 S1726193AbfBAVCf (ORCPT + 99 others); Fri, 1 Feb 2019 16:02:35 -0500 Received: from mx2.suse.de ([195.135.220.15]:51554 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725765AbfBAVCe (ORCPT ); Fri, 1 Feb 2019 16:02:34 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id E61D1ADF1; Fri, 1 Feb 2019 21:02:32 +0000 (UTC) Received: by quack2.suse.cz (Postfix, from userid 1000) id EA6941E1574; Fri, 1 Feb 2019 22:02:30 +0100 (CET) Date: Fri, 1 Feb 2019 22:02:30 +0100 From: Jan Kara To: Jerome Glisse Cc: Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Christian =?iso-8859-1?Q?K=F6nig?= , Jan Kara , Felix Kuehling , Jason Gunthorpe , Matthew Wilcox , Ross Zwisler , Dan Williams , Paolo Bonzini , Radim =?utf-8?B?S3LEjW3DocWZ?= , Michal Hocko , Ralph Campbell , John Hubbard , kvm@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-rdma@vger.kernel.org, linux-fsdevel@vger.kernel.org, Arnd Bergmann Subject: Re: [PATCH v4 0/9] mmu notifier provide context informations Message-ID: <20190201210230.GA11643@quack2.suse.cz> References: <20190123222315.1122-1-jglisse@redhat.com> <20190131161006.GA16593@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190131161006.GA16593@redhat.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 31-01-19 11:10:06, Jerome Glisse wrote: > > Andrew what is your plan for this ? I had a discussion with Peter Xu > and Andrea about change_pte() and kvm. Today the change_pte() kvm > optimization is effectively disabled because of invalidate_range > calls. With a minimal couple lines patch on top of this patchset > we can bring back the kvm change_pte optimization and we can also > optimize some other cases like for instance when write protecting > after fork (but i am not sure this is something qemu does often so > it might not help for real kvm workload). > > I will be posting a the extra patch as an RFC, but in the meantime > i wanted to know what was the status for this. > > Jan, Christian does your previous ACK still holds for this ? Yes, I still think the approach makes sense. Dan's concern about in tree users is valid but it seems you have those just not merged yet, right? Honza -- Jan Kara SUSE Labs, CR