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 706BFC05027 for ; Fri, 10 Feb 2023 18:58:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233082AbjBJS6c (ORCPT ); Fri, 10 Feb 2023 13:58:32 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46038 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232558AbjBJS6a (ORCPT ); Fri, 10 Feb 2023 13:58:30 -0500 Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4525F7B16B; Fri, 10 Feb 2023 10:58:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1676055509; x=1707591509; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=A03pmXrdhpVrzEP+7l9NWtjt5nMdZBxhCed5VX/Bfc0=; b=RjpjvYdu5WfHG/lpc6rFF5PK/SyLijIrar3NoG9SQwrqC+N16fl/kpl3 2mI8uB9s0jJQi2BHycADaSOiG0LP+IEhJSuhIrulL5BoFSBV+X/y8gQ3a SfMuvO0SUoXwFZTR+hF3dgCC6ZDyRjK2bGimW3cdUCVU/y6emXOE/yqJv QGgDD1lj5tpLwPWmbRA9FoAk9QibF0+UdMehtplSXDo5Z1hE/qSfYd6bs 2NDWfy0gJeOB6Q5DKXAch2xBjFU4zixdyeTp1sEx6NTldSGiFzSPybXoD Uz14YaPtvE1iq1eI0/OXGeghTuYnXag/Qe7p9TUZraKVGuRoYXJnzYTMB w==; X-IronPort-AV: E=McAfee;i="6500,9779,10617"; a="332637792" X-IronPort-AV: E=Sophos;i="5.97,287,1669104000"; d="scan'208";a="332637792" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Feb 2023 10:58:21 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10617"; a="756879427" X-IronPort-AV: E=Sophos;i="5.97,287,1669104000"; d="scan'208";a="756879427" Received: from hyekyung-mobl1.amr.corp.intel.com (HELO [10.209.82.221]) ([10.209.82.221]) by fmsmga003-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Feb 2023 10:58:18 -0800 Message-ID: <5e3fb10d-29d4-3272-674f-2bd6cb0540e1@intel.com> Date: Fri, 10 Feb 2023 10:58:18 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: [PATCH v5 06/14] x86/ioremap: Support hypervisor specified range to map as encrypted Content-Language: en-US To: Sean Christopherson , "Michael Kelley (LINUX)" Cc: Borislav Petkov , "hpa@zytor.com" , KY Srinivasan , Haiyang Zhang , "wei.liu@kernel.org" , Dexuan Cui , "luto@kernel.org" , "peterz@infradead.org" , "davem@davemloft.net" , "edumazet@google.com" , "kuba@kernel.org" , "pabeni@redhat.com" , "lpieralisi@kernel.org" , "robh@kernel.org" , "kw@linux.com" , "bhelgaas@google.com" , "arnd@arndb.de" , "hch@lst.de" , "m.szyprowski@samsung.com" , "robin.murphy@arm.com" , "thomas.lendacky@amd.com" , "brijesh.singh@amd.com" , "tglx@linutronix.de" , "mingo@redhat.com" , "dave.hansen@linux.intel.com" , Tianyu Lan , "kirill.shutemov@linux.intel.com" , "sathyanarayanan.kuppuswamy@linux.intel.com" , "ak@linux.intel.com" , "isaku.yamahata@intel.com" , "dan.j.williams@intel.com" , "jane.chu@oracle.com" , "tony.luck@intel.com" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , "linux-hyperv@vger.kernel.org" , "netdev@vger.kernel.org" , "linux-pci@vger.kernel.org" , "linux-arch@vger.kernel.org" , "iommu@lists.linux.dev" References: <1673559753-94403-1-git-send-email-mikelley@microsoft.com> <1673559753-94403-7-git-send-email-mikelley@microsoft.com> <4216dea6-d899-aecb-2207-caa2ae7db0e3@intel.com> From: Dave Hansen In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2/10/23 10:41, Sean Christopherson wrote: > Anyways, tying things back to the actual code being discussed, I vote against > CC_ATTR_PARAVISOR. Being able to trust device emulation is not unique to a > paravisor. A single flag also makes too many assumptions about what is trusted > and thus should be accessed encrypted. Did you like the more wordy per-device flags better? Or did you have something else in mind entirely?