Received: by 2002:a05:6358:11c7:b0:104:8066:f915 with SMTP id i7csp455297rwl; Wed, 5 Apr 2023 03:15:47 -0700 (PDT) X-Google-Smtp-Source: AKy350YEsh+i8L55bNQdPAeNm1Oe3lgUBTyjwcXRRMFssPzOiccChZjRChoY2UXSaO8VEVGGzkZB X-Received: by 2002:aa7:de8e:0:b0:502:9578:38ed with SMTP id j14-20020aa7de8e000000b00502957838edmr1344640edv.27.1680689746882; Wed, 05 Apr 2023 03:15:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1680689746; cv=none; d=google.com; s=arc-20160816; b=nNlL4X9CCHD1Zh+P+6qUwTz1AqqRehGPDVAySRLi2vA2IuQEoAIC+MIqkPEKU3zoWq jZBsLrq3F9p86CcXm518QX3SRz4VSgDawxpIlwtXxQz2Q6zFOPU8JRJzHNSWhtBTuQX7 9dKJ2TzCNXPrpmEWe3TzQGpO0ePluMNoIvdB7zq12I/nfIwDwvUkQSNuLDjY4Pc9d0W/ gwcu/VowWdKAs5K3GDw8uMS/gP7cbmPcd6YB4/IyTLI19NiLPDILdxvBiaxbpKXjqd/K F2rn+3QWUmb1bObzT8NTUVyP9tKmwCTfJO3T96JAZdEZVQ7Oy73As9aoYLutI9Kl50qP V4XQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=QtxKCZQq9P6gn2grmwTtfOWjbfdkBo+gZpF7sZrBSXo=; b=YhmQOQukCjITP564qEZvBh5/h7Qjrg2rZ8DQyY9+BtrnYImGy3JfnrPUK1W4+8u9AN /Jo+A+S5grMgoP7W582YH/RaEYUQdHSWRIkQUuL4ZQBm0FG78pSShmJz++PeGLZNOQ/P c0P/HvcD79y7reOs242l3dmltgqx7CrXPLV06QV3+132KWcuDmRHdXW9Lgw/nAhMiJRr s7GuKFDHRBjlwx+7FYIF0X5z4kQCI7FOYNB3kguQxu5XWsA5SDJzW9LdzITkNxOP8Czk RystKIihLHfNN//5E3iolPy5FoUXgIRP9xquOy/oBnqHiKfTs+trPBLyzxep6wRNUkwO jqZg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="b2W/2Dlw"; 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=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id h20-20020aa7de14000000b004acb5b5b339si2280185edv.219.2023.04.05.03.15.20; Wed, 05 Apr 2023 03:15:46 -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=@redhat.com header.s=mimecast20190719 header.b="b2W/2Dlw"; 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=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237568AbjDEKHD (ORCPT + 99 others); Wed, 5 Apr 2023 06:07:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54242 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237501AbjDEKHB (ORCPT ); Wed, 5 Apr 2023 06:07:01 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EB6671BD0 for ; Wed, 5 Apr 2023 03:06:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680689169; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=QtxKCZQq9P6gn2grmwTtfOWjbfdkBo+gZpF7sZrBSXo=; b=b2W/2Dlwi1r5J9mP8B82GRV9KqfjJBuYdZSMtbTlJp6qq3VB6lTENlLJDeqQIe0mNw3kUf eMxDtDgIXJ51bW6nEPSV6GmJ47mL347YrL0543C9xm76IFiXoqfBWKvDroOn6cVrtZJFV1 YFg95cqAMLDGB3nK0CBwZVng3ZpMo7M= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-630-mMkzMFZ3NGWUO3hz9QkDEw-1; Wed, 05 Apr 2023 06:06:08 -0400 X-MC-Unique: mMkzMFZ3NGWUO3hz9QkDEw-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 509DE280AA22; Wed, 5 Apr 2023 10:06:07 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.192.200]) by smtp.corp.redhat.com (Postfix) with ESMTPS id BF4CE400F4F; Wed, 5 Apr 2023 10:06:06 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 958C31800097; Wed, 5 Apr 2023 12:06:05 +0200 (CEST) Date: Wed, 5 Apr 2023 12:06:05 +0200 From: Gerd Hoffmann To: "Kirill A. Shutemov" Cc: Ard Biesheuvel , Dave Hansen , 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" , James Bottomley , Jiewen Yao , Erdem Aktas , "Kirill A. Shutemov" Subject: Re: [PATCH v7 6/6] x86/efi: Safely enable unaccepted memory in UEFI Message-ID: 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230404210153.tll2mojlglx4rfsa@box.shutemov.name> X-Scanned-By: MIMEDefang 3.1 on 10.11.54.10 X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2,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 Hi, > User will specify if it wants unaccepted memory or not for the VM. And if > it does it is his responsibility to have kernel that supports it. > > And you have not addressed my question: > > How is it different from any other feature the kernel is not [yet] aware > of? Come on. Automatic feature negotiation is standard procedure in many places. It's not like we inventing something totally new here. Just one example: When a virtio device learns a new trick a feature flag is added for it, and in case both guest and host support it it can be enabled, otherwise not. There is no need for the user to configure the virtio device features manually according to the capabilities of the kernel it is going to boot. take care, Gerd