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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS 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 658AEC433E6 for ; Mon, 8 Feb 2021 20:09:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 231CC64E8A for ; Mon, 8 Feb 2021 20:09:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236642AbhBHUJi (ORCPT ); Mon, 8 Feb 2021 15:09:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39106 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231529AbhBHSeb (ORCPT ); Mon, 8 Feb 2021 13:34:31 -0500 Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BAD4AC06178B for ; Mon, 8 Feb 2021 10:33:50 -0800 (PST) Received: by mail-qt1-x835.google.com with SMTP id w20so11062143qta.0 for ; Mon, 08 Feb 2021 10:33:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ziepe.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=zsGQUeCVE+9P7aNp54v7uYNj84EfUFjIYL1mjfYFnhM=; b=FVZOhOlO1m/ZSXYxWqQ3/Ohq3Wp/tvRDC8GTvP+9bSnDEiozixF3Jhu580CVCPRbPm HJk4/2MMunffgKDn9bqK046yfyDvCxzIoA7T9EVtyNZfNB349GjItsMZSxgoMAhgi9KK nGadbvWT0KrcPvYiuq0YMFcdBLGx2QWttauttC9CmU/yQLFXG/FJzLeOF3qlZ6ifMM/6 cG0R8kzOetckivQvI1vkoOdcGpp0+q8eD+xtEdsggBY1OP0qQ8kRpli+JjTQL4jj+cJE pYd3v7VG89h1Pnv0+WhajdC+jmuARDnJ7f5CKBccsE/96SEKVSqegmKaKZUt1ONCwfOI 3mqQ== 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=zsGQUeCVE+9P7aNp54v7uYNj84EfUFjIYL1mjfYFnhM=; b=jLDZ6vwlaLMndmKIO4cSuqvAX2HDGoW1STMcnw2sqRoJ+UehBCeqSWrb6dZcsypZkq S04Apwe7HHXBYrWqt/LEbImyb10z/J1gTPmX4IglG06+lBKDYSfPdDcKn9Kbc/mh7hrV urJ+DVPHWmzu3OLANcnrp1kKt7uDx4yIZdI1y9kHqd6O8fgws7IpFXgRangE8gwXgIBv Ma7zvxEboIJ+5tkOafLVa7jGyn8uWHo8pRfJwcUQYdFVNszsp5Qcyis3hQkmNHJGGJdg FuyQJW0RS0qwPkhPkdqXBBAJcT5u+683T2xT0QTrahjZ18Ccv6X7qhVe2e9UuEI30jtD Z+0g== X-Gm-Message-State: AOAM533kD1FIOA6qVfkHN+7C+P9gEkZ+UYrWC3XV1lmwTbVsWpq32CxF 241DWXeGYCalruG1sAV4d1DC3vuKGXVYBLdP X-Google-Smtp-Source: ABdhPJw9LB1ZweabsqrMBku5FA6d/KFYbPv37y2NqRoUt6oYBe0PrhVhU9GHDLJJPMyumQU59KaDBQ== X-Received: by 2002:aed:38e3:: with SMTP id k90mr16286292qte.119.1612809230040; Mon, 08 Feb 2021 10:33:50 -0800 (PST) Received: from ziepe.ca (hlfxns017vw-142-162-115-133.dhcp-dynamic.fibreop.ns.bellaliant.net. [142.162.115.133]) by smtp.gmail.com with ESMTPSA id p18sm16809839qkj.130.2021.02.08.10.33.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 08 Feb 2021 10:33:49 -0800 (PST) Received: from jgg by mlx with local (Exim 4.94) (envelope-from ) id 1l9BM4-005254-G1; Mon, 08 Feb 2021 14:33:48 -0400 Date: Mon, 8 Feb 2021 14:33:48 -0400 From: Jason Gunthorpe To: David Hildenbrand Cc: Zhou Wang , linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org, linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org, linux-api@vger.kernel.org, Andrew Morton , Alexander Viro , gregkh@linuxfoundation.org, song.bao.hua@hisilicon.com, kevin.tian@intel.com, jean-philippe@linaro.org, eric.auger@redhat.com, liguozhu@hisilicon.com, zhangfei.gao@linaro.org, Sihang Chen Subject: Re: [RFC PATCH v3 1/2] mempinfd: Add new syscall to provide memory pin Message-ID: <20210208183348.GV4718@ziepe.ca> References: <1612685884-19514-1-git-send-email-wangzhou1@hisilicon.com> <1612685884-19514-2-git-send-email-wangzhou1@hisilicon.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 08, 2021 at 09:14:28AM +0100, David Hildenbrand wrote: > People are constantly struggling with the effects of long term pinnings > under user space control, like we already have with vfio and RDMA. > > And here we are, adding yet another, easier way to mess with core MM in the > same way. This feels like a step backwards to me. Yes, this seems like a very poor candidate to be a system call in this format. Much too narrow, poorly specified, and possibly security implications to allow any process whatsoever to pin memory. I keep encouraging people to explore a standard shared SVA interface that can cover all these topics (and no, uaccel is not that interface), that seems much more natural. I still haven't seen an explanation why DMA is so special here, migration and so forth jitter the CPU too, environments that care about jitter have to turn this stuff off. Jason