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 79C3FC7EE29 for ; Thu, 8 Jun 2023 13:15:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236665AbjFHNPm (ORCPT ); Thu, 8 Jun 2023 09:15:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47136 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236628AbjFHNPj (ORCPT ); Thu, 8 Jun 2023 09:15:39 -0400 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C10AB26B3; Thu, 8 Jun 2023 06:15:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1686230134; x=1717766134; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=RHNSvXgy1i6qqzbOx4uNw2Wdc/hsK8aF/91zZPsKL3A=; b=CenOV2gncCGv4rOBhIfadWlucSXeeMoZkbQ7vvm/aF3lbHNIBsSuhaKc Y9tUXuKosveKmwzoqEG4Z0ozkPonyvfhJE3FBhnd/YMveBVcEO48P/FOG oGt/Kp03a/qNBRTMQCIt0iygKSynSBfDLh1BAR479D/HVsDFq11CKbp+5 DKUocFfP6uKi14fVtDkX2nNbcSD3G+SZMEmwa/wTYholeoRBvK98QsqtY yPkdjXOmigWu/A0I4SlDMoubIoHd9BIHsiGm3rAyHwQNt3/v5+oI5pHwp Td8ICKLok2Tsmo8CYyTk5r8VdO5il10jWWfZNdOpyu83RICY/4F291ECC w==; X-IronPort-AV: E=McAfee;i="6600,9927,10734"; a="337660974" X-IronPort-AV: E=Sophos;i="6.00,226,1681196400"; d="scan'208";a="337660974" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Jun 2023 06:13:12 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10734"; a="854337488" X-IronPort-AV: E=Sophos;i="6.00,226,1681196400"; d="scan'208";a="854337488" Received: from swalker-mobl1.amr.corp.intel.com (HELO [10.209.22.184]) ([10.209.22.184]) by fmsmga001-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Jun 2023 06:13:10 -0700 Message-ID: Date: Thu, 8 Jun 2023 06:13:10 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [PATCH v11 08/20] x86/virt/tdx: Get information about TDX module and TDX-capable memory Content-Language: en-US To: "kirill.shutemov@linux.intel.com" , "Huang, Kai" Cc: "kvm@vger.kernel.org" , "david@redhat.com" , "bagasdotme@gmail.com" , "ak@linux.intel.com" , "Wysocki, Rafael J" , "linux-kernel@vger.kernel.org" , "Chatre, Reinette" , "Christopherson,, Sean" , "pbonzini@redhat.com" , "tglx@linutronix.de" , "linux-mm@kvack.org" , "Yamahata, Isaku" , "Luck, Tony" , "peterz@infradead.org" , "Shahar, Sagi" , "imammedo@redhat.com" , "Gao, Chao" , "Brown, Len" , "sathyanarayanan.kuppuswamy@linux.intel.com" , "Huang, Ying" , "Williams, Dan J" References: <50386eddbb8046b0b222d385e56e8115ed566526.1685887183.git.kai.huang@intel.com> <20230608002725.xc25dantcwdxsuil@box.shutemov.name> <19ea7470e9d6fa698f9ad7caff3279873e530a0b.camel@intel.com> <20230608114128.vu75wlcojpyjak22@box.shutemov.name> From: Dave Hansen In-Reply-To: <20230608114128.vu75wlcojpyjak22@box.shutemov.name> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On 6/8/23 04:41, kirill.shutemov@linux.intel.com wrote: > These structures take 1.5K of memory and the memory will be allocated for > all machines that boots the kernel with TDX enabled, regardless if the > machine has TDX or not. It seems very wasteful to me. Actually, those variables are in .bss. They're allocated forever for anyone that runs a kernel that has TDX support.