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=-10.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable 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 EEA07C433EF for ; Thu, 2 Sep 2021 18:42:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D9E8E610E7 for ; Thu, 2 Sep 2021 18:42:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1347046AbhIBSm7 (ORCPT ); Thu, 2 Sep 2021 14:42:59 -0400 Received: from mail.kernel.org ([198.145.29.99]:34564 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1347038AbhIBSmx (ORCPT ); Thu, 2 Sep 2021 14:42:53 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 1EF57610A2; Thu, 2 Sep 2021 18:41:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1630608115; bh=6BoMcP5chkSrsK2RXEOXpWWeA5RODkgv0ciR/OeFF8g=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=axDU97TcWl+9FSZON5idbTgysIzP76JnTwD2j70wq7tXEJG584bESMkUgODDcoXmG 6h0E9pFLwN4xCMh7eji6pPQPs/K2m/m43kPVPem6kHCDQ7tk9Mlyhx++NPF3AcwXBs Kv3O0fGOGSPHbSOxgSBAdKOr4PG+KVRhtYEGdZBymVGSGOamZbyVNJwF6K2X+twFOl +FX0hC6Zsg5AfnH/DBVHfjJRIM8hYa8aVX/yf3WbDBFMM8KLCPx5Ypg05oUoyCZS9U BhweFV3VPwGpbLXpsnRi2iyaHG5zy3mF+GOn5ZoZ8byw5L6VBaDpcqBE7qp1TsQQNa 4esShkL525PWA== Subject: Re: [RFC] KVM: mm: fd-based approach for supporting KVM guest private memory To: Joerg Roedel Cc: Yu Zhang , David Hildenbrand , Sean Christopherson , Paolo Bonzini , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , kvm list , Linux Kernel Mailing List , Borislav Petkov , Andrew Morton , Andi Kleen , David Rientjes , Vlastimil Babka , Tom Lendacky , Thomas Gleixner , "Peter Zijlstra (Intel)" , Ingo Molnar , Varad Gautam , Dario Faggioli , the arch/x86 maintainers , linux-mm@kvack.org, linux-coco@lists.linux.dev, "Kirill A. Shutemov" , "Kirill A . Shutemov" , Sathyanarayanan Kuppuswamy , Dave Hansen References: <20210824005248.200037-1-seanjc@google.com> <307d385a-a263-276f-28eb-4bc8dd287e32@redhat.com> <20210827023150.jotwvom7mlsawjh4@linux.intel.com> <8f3630ff-bd6d-4d57-8c67-6637ea2c9560@www.fastmail.com> <20210901102437.g5wrgezmrjqn3mvy@linux.intel.com> From: Andy Lutomirski Message-ID: Date: Thu, 2 Sep 2021 11:41:53 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 9/2/21 2:27 AM, Joerg Roedel wrote: > On Wed, Sep 01, 2021 at 09:07:59AM -0700, Andy Lutomirski wrote: >> In principle, you could actually initialize a TDX guest with all of its >> memory shared and all of it mapped in the host IOMMU. > > Not sure how this works in TDX, but in SEV code fetches are always > treated as encrypted. So this approach would not work with SEV, not to > speak about attestation, which will not work with this approach either > :) > Oof.