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 7818BCE79DD for ; Wed, 20 Sep 2023 14:35:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234658AbjITOfn (ORCPT ); Wed, 20 Sep 2023 10:35:43 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37284 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232318AbjITOfm (ORCPT ); Wed, 20 Sep 2023 10:35:42 -0400 Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.126]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7D32AAD for ; Wed, 20 Sep 2023 07:35:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1695220537; x=1726756537; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=sH0b1baKbczKWombPJgtMInrODweXnPkKAuTu8OU4t0=; b=JGkbgwcoN93sF2o2dK7qMjtpPFtrK65pVZKKTZTffEH9Dp65jJROV3ce tHgV0OyRhZ7RFr/sGtxv0qx05X7PkMIIxi/z4KofzzLgt+dLsoVopCPK2 7/ZEo+qN3f0LcbtNoIUxWZat6BGKlHotsy3RmhL9v7PWs9ENdKWyZJjm9 jum0C18EkdIogd7vbXAAgw/iTmIi+48RzZ1W7ox3cVJaKV+JUH+rlnqNW orabbEQ0LGDXleOJf+DzbccdJ6XccdOmlwmpvcGq33REh/4Da6oITLNYZ fFOKyeBfgOSrfMUy+nlWLUK6nqJ+l/WMvfzxS6KtvEttJMmCF3xeHm/R/ A==; X-IronPort-AV: E=McAfee;i="6600,9927,10839"; a="365292557" X-IronPort-AV: E=Sophos;i="6.03,162,1694761200"; d="scan'208";a="365292557" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Sep 2023 07:35:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10839"; a="696318566" X-IronPort-AV: E=Sophos;i="6.03,162,1694761200"; d="scan'208";a="696318566" Received: from xiaoyaol-hp-g830.ccr.corp.intel.com (HELO [10.93.29.154]) ([10.93.29.154]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Sep 2023 07:35:31 -0700 Message-ID: Date: Wed, 20 Sep 2023 22:35:28 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.15.1 Subject: Re: [RFC PATCH v2 03/21] HostMem: Add private property and associate it with RAM_KVM_GMEM To: Markus Armbruster Cc: Paolo Bonzini , David Hildenbrand , Igor Mammedov , "Michael S. Tsirkin" , Marcel Apfelbaum , Richard Henderson , Peter Xu , =?UTF-8?Q?Philippe_Mathieu-Daud=c3=a9?= , Cornelia Huck , =?UTF-8?Q?Daniel_P=2e_Berrang=c3=a9?= , Eric Blake , Marcelo Tosatti , qemu-devel@nongnu.org, kvm@vger.kernel.org, Michael Roth , isaku.yamahata@gmail.com, Sean Christopherson , Claudio Fontana References: <20230914035117.3285885-1-xiaoyao.li@intel.com> <20230914035117.3285885-4-xiaoyao.li@intel.com> <8734zazeag.fsf@pond.sub.org> <878r91nvy4.fsf@pond.sub.org> Content-Language: en-US From: Xiaoyao Li In-Reply-To: <878r91nvy4.fsf@pond.sub.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On 9/20/2023 3:30 PM, Markus Armbruster wrote: > Xiaoyao Li writes: > >> On 9/19/2023 5:46 PM, Markus Armbruster wrote: >>> Xiaoyao Li writes: >>> >>>> From: Isaku Yamahata >>>> >>>> Add a new property "private" to memory backends. When it's set to true, >>>> it indicates the RAMblock of the backend also requires kvm gmem. >>> Can you add a brief explanation why you need the property? >> >> It provides a mechanism for user to specify whether the memory can serve as private memory (need request kvm gmem). > > Yes, but why would a user want such memory? > Because KVM demands it for confidential guest, e.g., TDX guest. KVM demands that the mem slot needs to have KVM_MEM_PRIVATE set and has valid gmem associated if the guest accesses it as private memory.