Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp649092rwl; Wed, 5 Apr 2023 06:04:03 -0700 (PDT) X-Google-Smtp-Source: AKy350a0C1V6HYe9762TM11jrwogqPFGr7/1qY+EIdQ94lB/BjUf9NXBNnpfD3KzuarLFFIkmQqg X-Received: by 2002:a17:906:a89:b0:933:9f43:5c3b with SMTP id y9-20020a1709060a8900b009339f435c3bmr3184152ejf.59.1680699842896; Wed, 05 Apr 2023 06:04:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680699842; cv=none; d=google.com; s=arc-20160816; b=tCFhUPJt3g1B91Ow63X4zC0pHokM+b/ydq+gY2QpA15Hb9eEV7Aea1hKPjwv2Ji4vV VtJEH5hitC1fir3GUbJMSYCbQlDkxE1OA4F1D2X4pzFeVI4dupmzw59cCoADwi63ZdFU Ck4x/2JFU17Wq1MAfD6XcJhM4c3SFjH29+jdLE1ecoMxNiha548GRStCJMyjw+6jeLbq PRpjIY2vpFuBiebAeCREHokc1Q1PpTA95xXCi3AYoPZKTcbkvpI7XWaM2P3VWv31MYqc gS2jIQSN0O/FBXkpdI/pFHlP+pY/3Nmu46lekGHein2EDsyuFHThxFdKX246GMfjGBbu kpCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=6RmPNrqfdsB0Mbfv2hoy46Be7thOjD79QYCY1+Vy7NY=; b=agtqa19pm3nBsdLX8ERxYlTEAvs+r3Qs5y5nR8k1z1qBzH19QmiCIOPUCVq0xL4I4V eOSpYLavb5mLtaOO2HVzxZHo4W07MNPxi19Y8XdTPJgqetSvfOxCLxcpmfNDT4E1bcN3 Udk6SsVGzZk1GSWlw8M9tiG42q30o5OdVpPFz41ko/4WiRT12WRa8TCQBzyScNY6Vcme uj2Cih7KNCwmXUef3aw/sYVNwt6oH6us6qX/w1EZgna11dSruDZJV+T2T5kopstevpQP yOuafYI3sm2uLpG/OQAoOb7HMhfmbjGfLxzaK0oC1jSq1dYay+ohnM8qb7Po2v2ut/XA 5VzQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=etjRcuSQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z23-20020a170906815700b0093018c7c47csi2331423ejw.10.2023.04.05.06.03.33; Wed, 05 Apr 2023 06:04:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=etjRcuSQ; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238101AbjDENCP (ORCPT + 99 others); Wed, 5 Apr 2023 09:02:15 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43856 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238116AbjDENCM (ORCPT ); Wed, 5 Apr 2023 09:02:12 -0400 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 83E2661BF for ; Wed, 5 Apr 2023 06:01:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1680699701; x=1712235701; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=nEsDOT4c3s2sCRVB0meEsVGfQxGhxGRSvgonugKmZ48=; b=etjRcuSQ7vPyfDDR/a09yj7998uWgc6GbJrWaRXWO58opMGJsheff18A HKCUGnjAb+ejxmbYGPbISRVQz5hqv1ORzhIby6NN15DZiK02hg6Ug2ReW EW6czdLUa2hJLwPoFIIs8/UirfBRh9kmm9VaaCHvMaJPWvaQj/mdtu1e+ jH6+2qR+hikpsVvLb9e6TnExNFT1pf9d0EVKJ0+DCjuRZSesQ4JmQ5UYX p+jdIv2YfybioWJ6zv8kZILGdPlnAZe3vaZ3jz4e/+C1lKeD7E4R6BYcm 1V6mo2jGOwgvg/WcIm3V1s2o5dhGsMu6WHC61eqqdRty03XKFwHajnOMT g==; X-IronPort-AV: E=McAfee;i="6600,9927,10670"; a="339935782" X-IronPort-AV: E=Sophos;i="5.98,319,1673942400"; d="scan'208";a="339935782" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Apr 2023 06:00:47 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10670"; a="664030958" X-IronPort-AV: E=Sophos;i="5.98,319,1673942400"; d="scan'208";a="664030958" Received: from kyunghyu-mobl2.amr.corp.intel.com (HELO [10.209.6.69]) ([10.209.6.69]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Apr 2023 06:00:46 -0700 Message-ID: Date: Wed, 5 Apr 2023 06:00:46 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH v7 6/6] x86/efi: Safely enable unaccepted memory in UEFI Content-Language: en-US To: Ard Biesheuvel , "Kirill A. Shutemov" Cc: Tom Lendacky , linux-kernel@vger.kernel.org, x86@kernel.org, Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "H. Peter Anvin" , Michael Roth , Joerg Roedel , Dionna Glaze , Andy Lutomirski , Peter Zijlstra , "Min M. Xu" , Gerd Hoffmann , James Bottomley , Jiewen Yao , Erdem Aktas , "Kirill A. Shutemov" References: <20230330114956.20342-1-kirill.shutemov@linux.intel.com> <1d38d28c2731075d66ac65b56b813a138900f638.1680628986.git.thomas.lendacky@amd.com> <20230404174506.pjdikxvk2fsyy4au@box.shutemov.name> <20230404180917.4fsgkzcdhqvph6io@box.shutemov.name> <20230404202445.6qkl7hz67qgievqz@box.shutemov.name> <20230404210153.tll2mojlglx4rfsa@box.shutemov.name> From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.9 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/5/23 00:46, Ard Biesheuvel wrote: > Once the firmware stops exposing this protocol (and ceases to accept > memory on the OS's behalf), we can phase it out from the kernel as > well. This is a part of the story that I have doubts about. How and when do you think this phase-out would happen, realistically? The firmware will need the unaccepted memory protocol support as long as there are guests around that need it, right? People like to keep running old kernels for a _long_ time. Doesn't that mean _some_ firmware will need to keep doing this dance for a long time? As long as there is firmware out there in the wild that people want to run new kernels on, the support needs to stay in mainline. It can't be dropped.