Received: by 2002:a05:6a10:6d10:0:0:0:0 with SMTP id gq16csp588531pxb; Thu, 21 Apr 2022 06:22:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxBgv4XXgIl5vzatthnWXb9Jy5IrtEOZ+qH3U/8xw6XQ0laLdHkeyUFgwPpSNtxzEKzZPMc X-Received: by 2002:a17:906:2bc1:b0:6cf:d009:7f6b with SMTP id n1-20020a1709062bc100b006cfd0097f6bmr22776663ejg.17.1650547370530; Thu, 21 Apr 2022 06:22:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1650547370; cv=none; d=google.com; s=arc-20160816; b=Li7531kbsWZgwNzBzErZ6HAAlUH9oEz/i2KYorDOqh6hA88suaP7GtNmpSJuJqPgsd 34iTO5iuLMqCry+CAVueIyLUg3IQU2wtRGws9fIEty1UmD9+dpQ2KDPmRd1xA8NHJ/2u dtQOo7X6dSUDOqcfbtYYBc974yXVQnVwrHSf747UypuJuQC4HM7sL7RqhyDhZMYwwnOz Ocx3ZfjGbQSieUSonZn1gWJO3w8j42pTwEjb6GUtJw990UMuz/roZHhIuBWoE7d+Lt+y CW1CVp3Fim5gsKqz9UVHRtRdNNnZjAKgyOy+CpIMQeRmYcQaaWHDim2GxtClyE1uycH1 dfLw== 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=37H/oibeiie1H68dJ8Ef/4/gLdoHYE2VEtUDb23g6Ms=; b=ulVgZsp69yP0YLivrYHGiEKsLD8QlSFmQn1DnTPJne6xGFhzDzVQp6SIou7gTnciSy khjtFF/e9bGbVq7WtocOp1NW4erGeXxyM5O+QeB6PFCMyMKdvUclQBVi4LZHf6rJBrEU msJpEfLK8Uu5PTrA/aJw+ZdoiGVCywYHoHCW5U0BywDSJ0MWTl5rLe6cV7ki8+rebKaa Zkf5pO/0pxozGCl1lyEty/WMcsdNnj3DV2+gEBLeOFkpW0o0u31S+WFFR6elU7wHgAj6 P1puB2XPp0kQL8xvoemFczRAKKUpm+tMPL6L6N99PvWUPAVgoyG5vbTaFJipz+dVcl4C 2BIw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=M3jCrsdD; 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 b2-20020a1709063ca200b006e8c9736e33si4320813ejh.51.2022.04.21.06.22.24; Thu, 21 Apr 2022 06:22:50 -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=M3jCrsdD; 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 S1353770AbiDTWO3 (ORCPT + 99 others); Wed, 20 Apr 2022 18:14:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47864 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1382763AbiDTWMg (ORCPT ); Wed, 20 Apr 2022 18:12:36 -0400 Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7C156C34; Wed, 20 Apr 2022 15:09:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1650492587; x=1682028587; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=H4xfv6xnEOb5EM82ED0+xKFwfPsnVvkv6xR9nOQGtlc=; b=M3jCrsdDEfVtUcXaoG4N6812XIXYShiknl+o03cXxYPjiris0pJA8CaL oG37lpjyP5+Ee+fZn5y8YAr8PCF/O/GBHDK9btf47foKuGwAuVefSpga0 1j3b8MYZirhZS83Un7BHi4hlhzkoH9Wx9cD+bp7Z3UfCCf9CpSFMQy59Q BaVzVXEc63r4tQe5VkpxQBiGK5/PlrwYLPweJOYMaFn4+kbl1PkuZNW5j 9tJ8pBZ24uCrSn4r88iBLzERAsnKGyJB8lAaXsPZwn2owiNzIOC6hg8z5 zFLi1m0ss45mLurKymK636w80W4Kx24IJ2JXzpxiCWxsIjGXbq7T4WD5a Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10323"; a="251472015" X-IronPort-AV: E=Sophos;i="5.90,276,1643702400"; d="scan'208";a="251472015" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Apr 2022 15:09:47 -0700 X-IronPort-AV: E=Sophos;i="5.90,276,1643702400"; d="scan'208";a="593355840" Received: from dmertma-mobl4.amr.corp.intel.com (HELO [10.209.83.57]) ([10.209.83.57]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Apr 2022 15:09:44 -0700 Message-ID: <088a3cbc-5d83-ca47-f544-087f0d59e331@linux.intel.com> Date: Wed, 20 Apr 2022 15:09:44 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0 Thunderbird/91.7.0 Subject: Re: [PATCH v3 4/4] platform/x86: intel_tdx_attest: Add TDX Guest attestation interface driver Content-Language: en-US To: Borislav Petkov Cc: Kai Huang , Thomas Gleixner , Ingo Molnar , Dave Hansen , x86@kernel.org, Hans de Goede , Mark Gross , "H . Peter Anvin" , "Kirill A . Shutemov" , Tony Luck , Andi Kleen , linux-kernel@vger.kernel.org, platform-driver-x86@vger.kernel.org References: <20220415220109.282834-1-sathyanarayanan.kuppuswamy@linux.intel.com> <20220415220109.282834-5-sathyanarayanan.kuppuswamy@linux.intel.com> <9198cc36-67d6-9365-5d18-f23ba4075151@linux.intel.com> From: Sathyanarayanan Kuppuswamy In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-9.0 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_EF,NICE_REPLY_A,RCVD_IN_DNSWL_MED, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_NONE 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 Hi Boris, On 4/20/22 3:00 PM, Borislav Petkov wrote: > On Tue, Apr 19, 2022 at 05:48:57AM -0700, Sathyanarayanan Kuppuswamy wrote: >> Make sense. We can just go with CONFIG_INTEL_TDX_ATTESTATION. > > Sounds like you didn't read my mail. Kai was questioning the need for a > Kconfig symbol at all. And me too. > > If this thing is not going to be used by anything else besides TDX > guests, why does it need a Kconfig option at all?! Sorry, it is a typo. I meant we can just compile it with TDX guest config (CONFIG_INTEL_TDX_GUEST). > >> Boris, this is a simple platform driver which adds IOCTL interfaces to allow >> user space to get TDREPORT and TDQuote support. >> >> So, would prefer to leave in platform/x86 or move it to arch/x86/coco/tdx/ ? > > See above. I agree with dropping the new CONFIG option. But regarding driver location, which is preferred (platform/x86/intel/tdx or arch/x86/coco/tdx/)? > -- Sathyanarayanan Kuppuswamy Linux Kernel Developer