From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-13.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E180EC433B4 for ; Mon, 10 May 2021 17:57:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C83A1611AB for ; Mon, 10 May 2021 17:57:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233333AbhEJR6a (ORCPT ); Mon, 10 May 2021 13:58:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54606 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233312AbhEJR6Y (ORCPT ); Mon, 10 May 2021 13:58:24 -0400 Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 442E0C061574 for ; Mon, 10 May 2021 10:57:19 -0700 (PDT) Received: by mail-pg1-x52f.google.com with SMTP id z16so13901603pga.1 for ; Mon, 10 May 2021 10:57:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=mWPrNb69nyGWKI0m9pPGW0IsoOENSpHi4HuteUPIllA=; b=WDir0qDOMsL25iK8wuf0VwNf0hPuuhOqUjjIVr1hs7XzcxFvbzfzYbFkdx/sh9mljA 1j3r5+a480WbR1tiGdAGMc75YHoI0pWIg1rBqEVgUfMYWxjA8ZHrhNHj2pd2/8iAlJB3 sfcnzbav23KQ6dzUy2Z0rWCgkThAw+d2CBVFPzYeT8htkYT+muYNLyNGbzHzWUMRWPUf 9tdzV2Im41JBWIiZLskLQGpj0ERl0rBZNSWHYrwPKUQD8N2F23w1M3xGeP8qAW2tMSoZ GUP5y2jtRz6EtzZTPRO0KyFrNDU+cJ0rqnkbYZuw1wJeYbmYfrrKCXk9NNQmDdnhDo8N GaNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=mWPrNb69nyGWKI0m9pPGW0IsoOENSpHi4HuteUPIllA=; b=IOFABZ+SrgKPnl4hMkXgy4LdDPV+vWPvs5uMNfVd9SfiRMsUo9QyZldTdskQzkLG4K /MThqKDcEa8pQccVgXlosHl20VApIHcMHVfv2wbQ6yXdAMkRoKc9teTfkj+8P9sue9qT 5mM9XhmMylmVzxNvQ/DpUe/KC0kZg91NJ4QuWRo064iPQVeQBeB7RroLY0W2+uhQCJUg O7A+nnaKjGS6rByLczDD9v0LCNbzNVHWLBmg4nB+EhPUf8kUOspv9tq9CkZQXI7u+wvg nhcu1LcA8a+fwPwe+vRoCIEHre36zXIRfsDWqkLhCE4OO5U5Ail4gczlWSobYzzBgzIB zC9A== X-Gm-Message-State: AOAM530bDT6c/jKBaMc21Q5QDOm7xcy8vrnkfA+vMIUt35/3Ao50odVE w6oQ6ia7WCMlMuGNfWWGy8GYew== X-Google-Smtp-Source: ABdhPJxGmr5OAWApep3UYINJrGM2ui/EZ9ttx3t/4ewaXx+5Bt9eSw10BXX2oHyBKAcRoxeHzRohHg== X-Received: by 2002:a62:d108:0:b029:25d:497e:2dfd with SMTP id z8-20020a62d1080000b029025d497e2dfdmr26602164pfg.29.1620669438673; Mon, 10 May 2021 10:57:18 -0700 (PDT) Received: from google.com (240.111.247.35.bc.googleusercontent.com. [35.247.111.240]) by smtp.gmail.com with ESMTPSA id s21sm11918766pjn.29.2021.05.10.10.57.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 10 May 2021 10:57:18 -0700 (PDT) Date: Mon, 10 May 2021 17:57:14 +0000 From: Sean Christopherson To: Jason Gunthorpe Cc: Daniel Vetter , Linus Torvalds , Tomasz Figa , Marek Szyprowski , Mauro Carvalho Chehab , DRI Development , LKML , Linux-MM , Linux ARM , Linux Media Mailing List , linux-samsung-soc , Paolo Bonzini Subject: Re: [PULL] topic/iomem-mmap-vs-gup Message-ID: References: <20210510135031.GF2047089@ziepe.ca> <20210510153412.GG2047089@ziepe.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210510153412.GG2047089@ziepe.ca> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org +Paolo On Mon, May 10, 2021, Jason Gunthorpe wrote: > On Mon, May 10, 2021 at 04:55:39PM +0200, Daniel Vetter wrote: > > > yeah vfio is still broken for the case I care about. I think there's > > also some questions open still about whether kvm really uses > > mmu_notifier in all cases correctly, > > IIRC kvm doesn't either. Yep, KVM on x86 has a non-trivial number of flows that don't properly hook into the mmu_notifier. Paolo is working on fixing the problem, but I believe the rework won't be ready until 5.14.