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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id C8F22C433F5 for ; Tue, 23 Nov 2021 15:20:33 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 2596C6B006C; Tue, 23 Nov 2021 10:20:18 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 209B06B0071; Tue, 23 Nov 2021 10:20:18 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 0AB5C6B0072; Tue, 23 Nov 2021 10:20:18 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0130.hostedemail.com [216.40.44.130]) by kanga.kvack.org (Postfix) with ESMTP id F1D616B006C for ; Tue, 23 Nov 2021 10:20:17 -0500 (EST) Received: from smtpin22.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id B6BCF80EF7E9 for ; Tue, 23 Nov 2021 15:20:07 +0000 (UTC) X-FDA: 78840555654.22.EA30B7E Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by imf13.hostedemail.com (Postfix) with ESMTP id ABCAE1046311 for ; Tue, 23 Nov 2021 15:20:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1637680806; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=nzZw5UfSegXbw18CEt/o6FXd1pUErV1MvwcNtl5mpBU=; b=OBAOQoQ+OjXQBBvUfiX/Iag1y6E3MDey9C1UVvmdAS4Mgq7Ds9rNVdwxVO4pNLFLcPQT5P XbEI0PV9eyddcHa7jGH9rUgOKXnxL8cnGNmPymxogimoKEQ3zLA0okfsDN0SEjejQtH0fE BbA+U9JibVD60PlN/je4HvskuZoYzeE= Received: from mail-wm1-f69.google.com (mail-wm1-f69.google.com [209.85.128.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-336-4BJ4GDfnO5KfS6UJNJb_BA-1; Tue, 23 Nov 2021 10:20:05 -0500 X-MC-Unique: 4BJ4GDfnO5KfS6UJNJb_BA-1 Received: by mail-wm1-f69.google.com with SMTP id r129-20020a1c4487000000b00333629ed22dso1369000wma.6 for ; Tue, 23 Nov 2021 07:20:05 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:organization:in-reply-to :content-transfer-encoding; bh=nzZw5UfSegXbw18CEt/o6FXd1pUErV1MvwcNtl5mpBU=; b=tVXX3xaZgJHmsZa1gjlbZLOE97bwAmr7T0Y5/sGlJ3y5BHqmkisrf+qRM9D6P3aVCa 5BMf2LUfl/adoDYTUqfybgNziFOQPYELwoE+bUcD0miDNWfsD6ne1IBi2GO7nUU1KqJd vqAr3UQHtoQ9WYK+It9+c0ToUNXfu68du5Ynq3jyhnlxzLxKoSu9MrlTopUCOWr5/1XU hTOfqwpJxuGSB0r6C/ORLwcnPUTJ8/DmTXvNYc7+vWVImWByvqHEiT3B9e1i+PiaKXgJ oBQ5W7FFsP7WJnCcm5I2PjtA8ECIWW8B09MhngO6YGyMOi1RfR0dkddhx112mxEZYbjm uMbw== X-Gm-Message-State: AOAM533975GIMJqWqAVRw9Wuukqmgc7OicEJ+hbmKDhnF9JmRnyFhcSC 0xDLKZ5oTIXkBr1kztpkgm6Qd45f79sammbEA3m4+XfRFWLtzkST6mxtj8OHNQLqPOk4/DCBERE Oc+MswyxP3FA= X-Received: by 2002:a05:6000:1681:: with SMTP id y1mr8183336wrd.52.1637680804551; Tue, 23 Nov 2021 07:20:04 -0800 (PST) X-Google-Smtp-Source: ABdhPJxUoSoPvPvLO49H6NY+gHF+4FNFe07RzaW7WxEc5sbe1D39sGgbrgj8rSNIcLf3gIFDDlAziw== X-Received: by 2002:a05:6000:1681:: with SMTP id y1mr8183284wrd.52.1637680804298; Tue, 23 Nov 2021 07:20:04 -0800 (PST) Received: from [192.168.3.132] (p5b0c6765.dip0.t-ipconnect.de. [91.12.103.101]) by smtp.gmail.com with ESMTPSA id n15sm1632169wmq.38.2021.11.23.07.20.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 23 Nov 2021 07:20:03 -0800 (PST) Message-ID: Date: Tue, 23 Nov 2021 16:20:02 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 Subject: Re: [RFC v2 PATCH 01/13] mm/shmem: Introduce F_SEAL_GUEST To: Paolo Bonzini , Jason Gunthorpe , Chao Peng Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, qemu-devel@nongnu.org, Jonathan Corbet , Sean Christopherson , 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 References: <20211119134739.20218-1-chao.p.peng@linux.intel.com> <20211119134739.20218-2-chao.p.peng@linux.intel.com> <20211119151943.GH876299@ziepe.ca> <6de78894-8269-ea3a-b4ee-a5cc4dad827e@redhat.com> From: David Hildenbrand Organization: Red Hat In-Reply-To: <6de78894-8269-ea3a-b4ee-a5cc4dad827e@redhat.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Server: rspam10 X-Rspamd-Queue-Id: ABCAE1046311 X-Stat-Signature: z6jec9uhoradjqndjc1e3sa588wftwam Authentication-Results: imf13.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b=OBAOQoQ+; dmarc=pass (policy=none) header.from=redhat.com; spf=none (imf13.hostedemail.com: domain of david@redhat.com has no SPF policy when checking 170.10.133.124) smtp.mailfrom=david@redhat.com X-HE-Tag: 1637680804-787364 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 23.11.21 10:06, Paolo Bonzini wrote: > On 11/19/21 16:39, David Hildenbrand wrote: >>> If qmeu can put all the guest memory in a memfd and not map it, then >>> I'd also like to see that the IOMMU can use this interface too so we >>> can have VFIO working in this configuration. >> >> In QEMU we usually want to (and must) be able to access guest memory >> from user space, with the current design we wouldn't even be able to >> temporarily mmap it -- which makes sense for encrypted memory only. The >> corner case really is encrypted memory. So I don't think we'll see a >> broad use of this feature outside of encrypted VMs in QEMU. I might be >> wrong, most probably I am:) > > It's not _that_ crazy an idea, but it's going to be some work to teach > KVM that it has to kmap/kunmap around all memory accesses. I'm also concerned about userspace access. But you sound like you have a plan :) -- Thanks, David / dhildenb