Received: by 2002:a05:6a10:9afc:0:0:0:0 with SMTP id t28csp1117664pxm; Thu, 3 Mar 2022 10:37:10 -0800 (PST) X-Google-Smtp-Source: ABdhPJwLN32aEe0lygJISVQ6S8y8YSNtUHR65lDHp6zCDMqbRIgmtQTW6n7j6Tlu4LninEiLRNAV X-Received: by 2002:a17:90a:a382:b0:1bc:202a:28e8 with SMTP id x2-20020a17090aa38200b001bc202a28e8mr6699066pjp.131.1646332630482; Thu, 03 Mar 2022 10:37:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1646332630; cv=none; d=google.com; s=arc-20160816; b=o7SRryS1J/G67y0rfjM0+JUBO6SnJVIfd3VQwbFyDbm+IKHn1wKrKaJacW3+4jSyoj V38racyWJ6ZpaQDCG1FjhRRnLjxW3B/cWCdUbWVs5QIwfqakGw3R0Zhyj9ZRkBYcEHoG +XjNx5zgOAoYLzn5gSaaGWfOqi6OmPivgFphk2+Ga4ORGznbux79oSPJyhePIDjE3Al5 SN+zA1BO9dIcg9ix63QBpq+LJNYAm6NeePpYkl6Rcd5xCIGbEp2GbOrC3fOUnoo5zCfa wSAybQLYl7iO0gqrl7l4axPlt8+lygNIcnpqSk3e6m5oxCDhRfd+qNZCyYFxbtXSnfj3 jsMQ== 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:subject :from:references:cc:to:content-language:user-agent:mime-version:date :message-id:dkim-signature; bh=PESjErUl/6k2vuPjRYNXLkwjYEOWZBRKISPuDN+MVfU=; b=Aq/xTqNEyXGBQk4sQlT9oKTEOjkJZrzDUjxH/WYwkSl8nqV96qZNHGBDbVbeEY9qXP aEGsT98+wH6BFgonjdCL9e1Xl3UyXjxcEecBke60A7g7icraSZ96el8SvNxRsTiJ1zI3 20Gtu2vQG6bTNVbDH4c6FEysT/qX13v9tSkygp6iuw3rNsGhMrWKu28ZFvcRDnLYDykj jwUqUqO4g0Ya3bMswJcdJ6dJ9i1JrLB4+DiRPAfoJaoGAOm0CGgjZ41qFUzbIzSsovKM dT/Ovf+edNutxcWX7z/t4mLOaP39wTKU6WDMSYKydBlZUCSZGIEun51QHZjx8GD2qlK4 OFrg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=IBsdkHHX; 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 j14-20020a170902da8e00b001519d27b998si2806791plx.328.2022.03.03.10.36.52; Thu, 03 Mar 2022 10:37:10 -0800 (PST) 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=IBsdkHHX; 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 S235250AbiCCRMD (ORCPT + 99 others); Thu, 3 Mar 2022 12:12:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42060 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230229AbiCCRMB (ORCPT ); Thu, 3 Mar 2022 12:12:01 -0500 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4E997188A35; Thu, 3 Mar 2022 09:11:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1646327475; x=1677863475; h=message-id:date:mime-version:to:cc:references:from: subject:in-reply-to:content-transfer-encoding; bh=vaOGjw7VdBKeP6eHbl1iLmTW0NFWNNn5qWcGsk5ZbQE=; b=IBsdkHHXV4wbifK/fQcmch4j2dCl+OIeR+9I3TJLZJbc+X/7oOpfuHrQ hdqWWgZKCK/GlUACOQgFuuVbD0kKsFRoFPX0tZLLV0DZKF5Lief0biL/g uJSJbwueN8QPoCzBPrzyqVHRWB26Lyd+6hL+oQ1UmpJAtO/Y9OtgKdJuP fSkQOcrY2PA1x2FHWQULaGWNOneVdNkWhFJ+ViFama+IcUdAjTLHxJC+1 u4vGQ5U4RrxBvO/rfHAEqcp1ymommJHwYMuC3273UixpEI8nyE/ortQ+7 Utv5idK+y1GauVyHG025EgKtJwZraG+BGZQUwgdoDFfr2W9pbSunDNdCV g==; X-IronPort-AV: E=McAfee;i="6200,9189,10275"; a="253928899" X-IronPort-AV: E=Sophos;i="5.90,151,1643702400"; d="scan'208";a="253928899" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Mar 2022 09:09:44 -0800 X-IronPort-AV: E=Sophos;i="5.90,151,1643702400"; d="scan'208";a="642184867" Received: from eabada-mobl2.amr.corp.intel.com (HELO [10.209.6.252]) ([10.209.6.252]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Mar 2022 09:09:43 -0800 Message-ID: <5ca2583b-a873-fc5d-ece6-d4bdbd133a89@intel.com> Date: Thu, 3 Mar 2022 09:09:37 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Content-Language: en-US To: Brijesh Singh , x86@kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, linux-efi@vger.kernel.org, platform-driver-x86@vger.kernel.org, linux-coco@lists.linux.dev, linux-mm@kvack.org Cc: Thomas Gleixner , Ingo Molnar , Joerg Roedel , Tom Lendacky , "H. Peter Anvin" , Ard Biesheuvel , Paolo Bonzini , Sean Christopherson , Vitaly Kuznetsov , Jim Mattson , Andy Lutomirski , Dave Hansen , Sergio Lopez , Peter Gonda , Peter Zijlstra , Srinivas Pandruvada , David Rientjes , Dov Murik , Tobin Feldman-Fitzthum , Borislav Petkov , Michael Roth , Vlastimil Babka , "Kirill A . Shutemov" , Andi Kleen , "Dr . David Alan Gilbert" , brijesh.ksingh@gmail.com, tony.luck@intel.com, marcorr@google.com, sathyanarayanan.kuppuswamy@linux.intel.com References: <20220224165625.2175020-1-brijesh.singh@amd.com> <20220224165625.2175020-23-brijesh.singh@amd.com> From: Dave Hansen Subject: Re: [PATCH v11 22/45] x86/sev: Use SEV-SNP AP creation to start secondary CPUs In-Reply-To: <20220224165625.2175020-23-brijesh.singh@amd.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NICE_REPLY_A, RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham 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 2/24/22 08:56, Brijesh Singh wrote: > + /* > + * Allocate VMSA page to work around the SNP erratum where the CPU will > + * incorrectly signal an RMP violation #PF if a large page (2MB or 1GB) > + * collides with the RMP entry of VMSA page. The recommended workaround > + * is to not use a large page. > + * > + * Allocate one extra page, use a page which is not 2MB-aligned > + * and free the other. > + */ > + p = alloc_pages(GFP_KERNEL_ACCOUNT | __GFP_ZERO, 1); > + if (!p) > + return NULL; > + > + split_page(p, 1); > + > + pfn = page_to_pfn(p); > + if (IS_ALIGNED(__pfn_to_phys(pfn), PMD_SIZE)) { > + pfn++; > + __free_page(p); > + } else { > + __free_page(pfn_to_page(pfn + 1)); > + } > + > + return page_address(pfn_to_page(pfn)); > +} This can be simplified. There's no need for all the sill pfn_to_page() conversions or even an alignment check. The second page (page[1]) of an order-1 page is never 2M/1G aligned. Just use that: // Alloc an 8k page which is also 8k-aligned: p = alloc_pages(GFP_KERNEL_ACCOUNT | __GFP_ZERO, 1); if (!p) return NULL; split_page(p, 1); // Free the first 4k. This page _may_ // be 2M/1G aligned and can not be used: __free_page(p); // Return the unaligned page: return page_address(p+1);