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 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5D6F0C433F5 for ; Fri, 19 Nov 2021 19:18:10 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 46DA961B1B for ; Fri, 19 Nov 2021 19:18:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234456AbhKSTVH (ORCPT ); Fri, 19 Nov 2021 14:21:07 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41018 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232663AbhKSTVH (ORCPT ); Fri, 19 Nov 2021 14:21:07 -0500 Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1C81AC06173E for ; Fri, 19 Nov 2021 11:18:05 -0800 (PST) Received: by mail-pj1-x102f.google.com with SMTP id gx15-20020a17090b124f00b001a695f3734aso9659400pjb.0 for ; Fri, 19 Nov 2021 11:18:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=g/YNskCC8H0pIrRty3bOxTWWIwZezM/dF8uipgTGVfY=; b=CNOzkM2IBiGjqfRhSRYpA8+aOR9+w9kYa1mO17Fub/lEhXiodlJQQbYvAU23XPSB80 zEPvGqgAhRJ6Ac9fwqtRfF+TRjsCcSQq5iPvk/1Ntl7JnciUfiF+ZDILvu0CHa2qGnpl ujk4JKugJX/qAenq8IEMYsdgtnjBtqpUR91i9SBdt8L7pGQrEmbiL4/gffr02rrMSJmz 6yzyBXWa8jt0zBA9CA494YG0zM4LbpueA4wdoIYm5oesyznYRillp/PJwv9KFNX7usVm 7PTxEHROAZHj6Qj+AaUATSaSV1EpFTybV/lhNnk/ZpIoUTNLB6A6TpiLrhOQ7Y6XFsOL ut9g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=g/YNskCC8H0pIrRty3bOxTWWIwZezM/dF8uipgTGVfY=; b=o43ysm8jvTMvI3SZP4tZW49LC1MP92fGjPCo54mhzHWzjkbSdOyIKLXYEcls3pXPe1 gCBvye32pdl7lHJsB77/2kFXitBw0jIGlqx1UZtVhCqH0kTYtdX6m+JD+AdTOkE8QiEp 8lz/cogveo1JC7Vs2jlzA18iFdIQPIq0eWwAXUpwbZQJ5qLfztYwi/2G1LNDo8C25VTr Ddzd249gIUUpRyEUaEg6piVle9rLyL9nQm5vusQnas2K1+m9eas69v7t5aNwRLQHi3e7 EU/dUO8JqEg2PHyAY6iY/jwDZjjQ+9LwUS3/VcARz21w5DAXzmicNFKuCKeKA9si/c1S 1aAA== X-Gm-Message-State: AOAM532PMcQx2G7J2V41e008Jz0MgJ5/w0klHCwRPqnTeHZdACziU6HM yQ4beN67/DJPcUUry5WeIdBMUg== X-Google-Smtp-Source: ABdhPJxLPt6CntmozfnHLwXqny0KwCU2vgLZSjJXfMA4iRfgP9luxNnbV0AtIM87S/ieQOg/r1KAAQ== X-Received: by 2002:a17:902:b28a:b0:142:3e17:38d8 with SMTP id u10-20020a170902b28a00b001423e1738d8mr80638372plr.56.1637349484440; Fri, 19 Nov 2021 11:18:04 -0800 (PST) Received: from google.com (157.214.185.35.bc.googleusercontent.com. [35.185.214.157]) by smtp.gmail.com with ESMTPSA id f15sm426180pfe.171.2021.11.19.11.18.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 19 Nov 2021 11:18:03 -0800 (PST) Date: Fri, 19 Nov 2021 19:18:00 +0000 From: Sean Christopherson To: David Hildenbrand Cc: Jason Gunthorpe , Chao Peng , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, qemu-devel@nongnu.org, Paolo Bonzini , Jonathan Corbet , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , Thomas Gleixner , Ingo Molnar , Borislav Petkov , x86@kernel.org, "H . Peter Anvin" , Hugh Dickins , Jeff Layton , "J . Bruce Fields" , Andrew Morton , Yu Zhang , "Kirill A . Shutemov" , luto@kernel.org, john.ji@intel.com, susie.li@intel.com, jun.nakajima@intel.com, dave.hansen@intel.com, ak@linux.intel.com Subject: Re: [RFC v2 PATCH 01/13] mm/shmem: Introduce F_SEAL_GUEST Message-ID: References: <20211119134739.20218-1-chao.p.peng@linux.intel.com> <20211119134739.20218-2-chao.p.peng@linux.intel.com> <20211119151943.GH876299@ziepe.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Fri, Nov 19, 2021, David Hildenbrand wrote: > On 19.11.21 16:19, Jason Gunthorpe wrote: > > As designed the above looks useful to import a memfd to a VFIO > > container but could you consider some more generic naming than calling > > this 'guest' ? > > +1 the guest terminology is somewhat sob-optimal. For the F_SEAL part, maybe F_SEAL_UNMAPPABLE? No ideas for the kernel API, but that's also less concerning since it's not set in stone. I'm also not sure that dedicated APIs for each high-ish level use case would be a bad thing, as the semantics are unlikely to be different to some extent. E.g. for the KVM use case, there can be at most one guest associated with the fd, but there can be any number of VFIO devices attached to the fd.