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 A50D4EE499E for ; Fri, 18 Aug 2023 23:15:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242193AbjHRXOz (ORCPT ); Fri, 18 Aug 2023 19:14:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35338 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S241858AbjHRXOg (ORCPT ); Fri, 18 Aug 2023 19:14:36 -0400 Received: from mail-pg1-x54a.google.com (mail-pg1-x54a.google.com [IPv6:2607:f8b0:4864:20::54a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E46E030C2 for ; Fri, 18 Aug 2023 16:14:34 -0700 (PDT) Received: by mail-pg1-x54a.google.com with SMTP id 41be03b00d2f7-563ab574cb5so1798863a12.1 for ; Fri, 18 Aug 2023 16:14:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1692400474; x=1693005274; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=5DZepNUwrlYIieQTJr9Dh/3tOxOseVHo5Xld8dMNuNg=; b=lsQ+HVzfe/LvJcjpi5EkUeNksPQ4SKFkDuitTo8QZ8/V1sWcr6kxph8TKOQUDPuQY6 3R+Pf/jmvF5hwJvwA/qd5EZ3umv7mDUrFv27YvRHTc8kZljL+me7hAdDiSfTlWvFfEj/ coNhxIPQ3jfxMfHlGddYmQDEEwSQ+Y5RTQnvOpYtmp6kPuX7mXVgS6zWmHmU+sPbmIdm 3HwG+UlgYVsM7jRmT+4vVPawxf3yitDSjepBo5MpteRZM1D0Vdl8EmV210P/oEzmRyXa r4YJEufogWKx1B2Git+TQpUucYnwL9g/7hgB267fQrq1A8h/ysQfdzEjFcPJQrGcpD54 aN0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692400474; x=1693005274; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=5DZepNUwrlYIieQTJr9Dh/3tOxOseVHo5Xld8dMNuNg=; b=jqHz5S8a7mavwMxs/cjgtnwVea8gQf0hW7tndlUKaDB5eMknGIeptIDOfa/ESwLf/b Ok9g1V2ac0Yb18dmmLlQJ8pOKPn4K4gk7ELtsRcUw3rNIAN0IOkROiDFBclJkrIqlQkt XA2iXZq/PqyUljBkTbgF+/iK0T5B3Og3eVaH++UK0822I+utu2bf4kHgUdWcTBt7YzDl 4ulkzS80wmz8A4wCPCUCKWz3UFjqH9h5jelaVIOssqTRipwSTUi+svDxZIdQ8R5TiCb7 z8JJHJ8PV9b94SOtWI5g5Ms4kh7B7e9ec85ZO5HLHW3q8oo6V1yuec6CVaQzNB3Kx7mY DrsA== X-Gm-Message-State: AOJu0YxyiAy+ws5GY+FnUpzY1IC5W/8aiO+xalmQVztvAfIDM917OTLK E2q+b1emhbrNFczY3bDP7oM/IQHzGug= X-Google-Smtp-Source: AGHT+IF9HyPZ8NYi1dOCnWJqmB9Xg8StOO2+i4hjQBZ6kPAEn5MgrO+XU77nUxSPGBzB9RxPZ8c5rXOzSME= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a63:3ecd:0:b0:565:56be:4dee with SMTP id l196-20020a633ecd000000b0056556be4deemr124213pga.8.1692400474224; Fri, 18 Aug 2023 16:14:34 -0700 (PDT) Date: Fri, 18 Aug 2023 16:14:18 -0700 In-Reply-To: Mime-Version: 1.0 References: X-Mailer: git-send-email 2.42.0.rc1.204.g551eb34607-goog Message-ID: <169239820500.1761806.6161030396328593760.b4-ty@google.com> Subject: Re: [PATCH 0/8] KVM: gmem: Adding hooks for SEV and TDX From: Sean Christopherson To: Sean Christopherson , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, isaku.yamahata@intel.com Cc: isaku.yamahata@gmail.com, Michael Roth , Paolo Bonzini , erdemaktas@google.com, Sagi Shahar , David Matlack , Kai Huang , Zhi Wang , chen.bo@intel.com, linux-coco@lists.linux.dev, Chao Peng , Ackerley Tng , Vishal Annapurve , Yuan Yao , Jarkko Sakkinen , Xu Yilun , Quentin Perret , wei.w.wang@intel.com, Fuad Tabba Content-Type: text/plain; charset="utf-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 15 Aug 2023 10:18:47 -0700, isaku.yamahata@intel.com wrote: > From: Isaku Yamahata > > This patch series for KVM guest memfd is to have common code base for SEV and > TDX. Several minor fixes. Based on this patch series, TDX KVM can defer page > clearing without mmu lock. > > Isaku Yamahata (6): > KVM: gmem: Make kvm_gmem_bind return EBADF on wrong fd > KVM: gmem: removed duplicated kvm_gmem_init() > KVM: gmem: Fix kvm_gmem_issue_arch_invalidate() > KVM: gmem: protect kvm_mmu_invalidate_end() > KVM: gmem: Avoid race with kvm_gmem_release and mmu notifier > RFC: KVM: gmem: Guarantee the order of destruction > > [...] Applied patches 1 and 2 to kvm-x86 guest_memfd. I'll post the alternative approach for fixing the unlocking bug next week (need to test, and I'm out of time this week). Regarding the initialize/invalidate hooks, I resurrected the discussion from the previous version[*], I'd like to bottom out on a solution in that thread before applying anything. [*] https://lore.kernel.org/all/ZN%2FwY53TF2aOZtLu@google.com [1/8] KVM: gmem: Make kvm_gmem_bind return EBADF on wrong fd https://github.com/kvm-x86/linux/commit/07ac04fbefce [2/8] KVM: gmem: removed duplicated kvm_gmem_init() https://github.com/kvm-x86/linux/commit/9ab46d91d5ea -- https://github.com/kvm-x86/linux/tree/next https://github.com/kvm-x86/linux/tree/fixes