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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 50464C433EF for ; Wed, 30 Mar 2022 19:47:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231285AbiC3Tt0 (ORCPT ); Wed, 30 Mar 2022 15:49:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35844 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231164AbiC3TtX (ORCPT ); Wed, 30 Mar 2022 15:49:23 -0400 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 EEA9149FA5 for ; Wed, 30 Mar 2022 12:47:37 -0700 (PDT) Received: by mail-pj1-x102f.google.com with SMTP id mr5-20020a17090b238500b001c67366ae93so689829pjb.4 for ; Wed, 30 Mar 2022 12:47:37 -0700 (PDT) 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=oOXYySrw0TmLydZhFaBm1sSWPMqWsbFjnghNvkA6FaM=; b=gbpzu1Z2hU6QehteHeEJKFYONUPWrH2ePmFVq8fBFUmfdYtEiqsX50/mxXE6MurCVz JXAqXdvNZvb7vA7qoEoc3FanAyDiRoKv7/syIKrdi6n09xaXb/qIZgA4k61JPaUcBbAY SUfoMNlirJfv7ZV/HVRE0iKvnYT0V0CkAEz1G+3n17fFVaVBxVr3ZhxMjObOo6cbFX1W lnCCzZ4T0f2CXnM+WbG/wctlV1md8NG+uBIWqM3+eDO3X31aMD3bFQEAU6e+drFhi8qj xVoa+Awu1NON5/2ATU7EsXqpafSe/P2WYIYgWuGSTcu7yldqZkm0g6v6L3y/OhP50dsQ Ln5g== 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=oOXYySrw0TmLydZhFaBm1sSWPMqWsbFjnghNvkA6FaM=; b=ZwxNkjX9IbKvQQkssxxgvWfJ9yB+we+2cfBWRM2fUudCUga5Z9OUl7uhs0zf6iqmj3 hIbQsugEMj7gHUQlRe4q0bf+eovq8SqmVFh0R0KAmQNTgBUUyBZSKHYPNXR/rn1QVJ0X YhhMIFJL82Nw095JHqZFcK02BPAuFd6w1POvhd73ysUrt/Qcr1ku4TPgB4eGkGXVtpVP ntC7rJfBhHM7upgwi/U9qm4v8p2dUmKCOP3wXTFuohDBNyNnJqZ2Oo11B11DircfwS30 KX3hvq+mfUJYPXC0BXwGcWTcmomDXZLVICs0DoHnPYKVTNhG0Yj0Jd0qwQ5EXP+TLwL0 Q6Cg== X-Gm-Message-State: AOAM530Cz7iHCMGcbHgLxeYONZStZ2rEn46ymuzaJ3ZluSTNqcFFIZSf 9jsv9lv3czUeJltsniA3qRbcSw== X-Google-Smtp-Source: ABdhPJxk2VhMZr3qV/kmbltDEUGnT8rnmM3fOZ/vJPdGZY8jeavTdQllY8SLAsXjHwz5J/UF08rS1w== X-Received: by 2002:a17:90b:3846:b0:1c6:841b:7470 with SMTP id nl6-20020a17090b384600b001c6841b7470mr1252259pjb.193.1648669657261; Wed, 30 Mar 2022 12:47:37 -0700 (PDT) Received: from google.com (157.214.185.35.bc.googleusercontent.com. [35.185.214.157]) by smtp.gmail.com with ESMTPSA id ij17-20020a17090af81100b001c67c964d93sm8557230pjb.2.2022.03.30.12.47.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 30 Mar 2022 12:47:36 -0700 (PDT) Date: Wed, 30 Mar 2022 19:47:33 +0000 From: Sean Christopherson To: "Nikunj A. Dadhania" Cc: Paolo Bonzini , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , Brijesh Singh , Tom Lendacky , Peter Gonda , Bharata B Rao , "Maciej S . Szmigiero" , Mingwei Zhang , David Hildenbrand , kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RFC v1 0/9] KVM: SVM: Defer page pinning for SEV guests Message-ID: References: <20220308043857.13652-1-nikunj@amd.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 Wed, Mar 30, 2022, Nikunj A. Dadhania wrote: > On 3/29/2022 2:30 AM, Sean Christopherson wrote: > > Let me preface this by saying I generally like the idea and especially the > > performance, but... > > > > I think we should abandon this approach in favor of committing all our resources > > to fd-based private memory[*], which (if done right) will provide on-demand pinning > > for "free". > > I will give this a try for SEV, was on my todo list. > > > I would much rather get that support merged sooner than later, and use > > it as a carrot for legacy SEV to get users to move over to its new APIs, with a long > > term goal of deprecating and disallowing SEV/SEV-ES guests without fd-based private > > memory. > > > That would require guest kernel support to communicate private vs. shared, > > Could you explain this in more detail? This is required for punching hole for shared pages? Unlike SEV-SNP, which enumerates private vs. shared in the error code, SEV and SEV-ES don't provide private vs. shared information to the host (KVM) on page fault. And it's even more fundamental then that, as SEV/SEV-ES won't even fault if the guest accesses the "wrong" GPA variant, they'll silent consume/corrupt data. That means KVM can't support implicit conversions for SEV/SEV-ES, and so an explicit hypercall is mandatory. SEV doesn't even have a vendor-agnostic guest/host paravirt ABI, and IIRC SEV-ES doesn't provide a conversion/map hypercall in the GHCB spec, so running a SEV/SEV-ES guest under UPM would require the guest firmware+kernel to be properly enlightened beyond what is required architecturally.