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 B3B74C4167B for ; Fri, 9 Dec 2022 13:25:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229738AbiLINZu (ORCPT ); Fri, 9 Dec 2022 08:25:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40842 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229677AbiLINZj (ORCPT ); Fri, 9 Dec 2022 08:25:39 -0500 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5DA8E3FB95 for ; Fri, 9 Dec 2022 05:25:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1670592338; x=1702128338; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=BSrPUYonGntiTXzc7J4wwmhKstgGiqEhA6jFvc+d+NI=; b=aKP5ek4m6ufnjFSsZr7brhDvHBoiyxXfpexg5mLP9DXFHtCnUrfFxK2U OU834nMm7MbPZE9P0Eu2seUuRZSeWIHyy8VzdSX/1j9xhVCEfpJ8j9sin KW4obKwa4k6xZZlVj+zn1qchPXfX75Ie6g4ItR5/50MY+htQ9KwoydpUg hzR8T9BIPvDffUDhsEaKh54Bq0H824mlrKoSSwZFyS3dkRFaOxEwwt51F aZBXGsudB85hdtstVSegeO7O30QJrm4tMXFn6h4nckSuDOPy1JfOjAdNi G2aE7PAaH+9Df2ISmfJe9bcuhBjlHrhO99/SfvYwwCYcjmNyRbLQphcJQ g==; X-IronPort-AV: E=McAfee;i="6500,9779,10556"; a="317483319" X-IronPort-AV: E=Sophos;i="5.96,230,1665471600"; d="scan'208";a="317483319" Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Dec 2022 05:25:36 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10556"; a="892670382" X-IronPort-AV: E=Sophos;i="5.96,230,1665471600"; d="scan'208";a="892670382" Received: from elinares-mobl.ger.corp.intel.com (HELO box.shutemov.name) ([10.249.38.98]) by fmsmga006-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Dec 2022 05:25:33 -0800 Received: by box.shutemov.name (Postfix, from userid 1000) id 3AACD109CE2; Fri, 9 Dec 2022 16:25:31 +0300 (+03) From: "Kirill A. Shutemov" To: Dave Hansen , Borislav Petkov , Andy Lutomirski Cc: Kuppuswamy Sathyanarayanan , Thomas Gleixner , Elena Reshetova , x86@kernel.org, linux-coco@lists.linux.dev, linux-kernel@vger.kernel.org, "Kirill A. Shutemov" Subject: [PATCH 0/4] x86/tdx: Changes for TDX guest initialization Date: Fri, 9 Dec 2022 16:25:20 +0300 Message-Id: <20221209132524.20200-1-kirill.shutemov@linux.intel.com> X-Mailer: git-send-email 2.38.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Several changes to TDX initialization: - Make early panic message visible to user; - Relax SEPT_VE_DISABLE for debug TD. It helps to investigate bugs resulting in access of unaccepted memory. - Make sure NOTIFY_ENABLES is off to eliminate possible source of random #VE. The patchset makes use of ReportFatalError TDVMCALL. The definition of the TDVMCALL has changed in recent GHCI update[1]. It now requires more arguments handled by __tdx_hypercall(). The patch that expands __tdx_hypercall() is the same as the patch included in TDX guest enabling for Hyper-V. [1] https://cdrdv2.intel.com/v1/dl/getContent/726790 Kirill A. Shutemov (4): x86/tdx: Expand __tdx_hypercall() to handle more arguments x86/tdx: Use ReportFatalError to report missing SEPT_VE_DISABLE x86/tdx: Relax SEPT_VE_DISABLE check for debug TD x86/tdx: Disable NOTIFY_ENABLES arch/x86/coco/tdx/tdcall.S | 82 ++++++++++++++++++++++--------- arch/x86/coco/tdx/tdx.c | 57 ++++++++++++++++++++- arch/x86/include/asm/shared/tdx.h | 6 +++ arch/x86/kernel/asm-offsets.c | 6 +++ 4 files changed, 125 insertions(+), 26 deletions(-) -- 2.38.0