Received: by 2002:a05:6a10:9e8c:0:0:0:0 with SMTP id y12csp265600pxx; Thu, 29 Oct 2020 01:59:06 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwSzFxb0A6EGhousYTu6JjR6RWpEXmi5Qc3F95Gd5GCsS702EMoHCJLfEPLh5p9FzKNJ6Ag X-Received: by 2002:aa7:d64e:: with SMTP id v14mr3006986edr.66.1603961946556; Thu, 29 Oct 2020 01:59:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603961946; cv=none; d=google.com; s=arc-20160816; b=glzQhrCadxRGs7lwVBDJ6hf9PqjN0AluSiDUuez5a5xtwyohGCr/7FhpECjPXD8iLW HYt9AuG18Y225H8ZnbkdXIhk3ZTQaICewiHSZL8ywqCdL6im1vuKM99nZZz0T46ozCCE J3Wpjnl3UCdlg9ZbD4RXPUq8sjyp42DV/BeHmSvfDR1IA9fXGgmFGOH5CEpJYGOPE4J/ aUd74sQ5XtYY/0mIvv3kdHWWgBdtB5Tj/JVO2Gvq/S31X7NSJU6AUcnGusoPWlI0g9Ai wQiCkfMm4q9Y4bAgX4Lx9Qw7No3mshB0Gb9KWG2J6p2wmUFwUF5lranQGfRsCBsfRAb4 PI2Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=aEJlKLF0pOoynsBe3/MpV9vkPAazTer78aIak3Yh4iI=; b=dOwAgLDEJBR9I+e4ra3L9Eb4U7g6xCHcJMq3LUrajAtp6KRtoMOi8MnIXxaMy30dYw P7SiUrhB1BgbMRYaxSdLHcCMyq1sj/A4d8zfvYHSLVK3RzpIIUesujm7b5FbhqIzyGwB 7ON06ROGeuTnI0jga0GIL/n0vPCdFxn9Rtp/T0/wNwDQou67XW40qwYzJkdrIWnsbFaq N1Jn4SzBp82W5H3c4UWysXdb76WoN/20zwWgtSFUZ0flqM1UxtZ6Kv/JiKSU21dIuNe6 wItRmBAeV1BcxtiwnGDJcHbIYUxQP57eOJVIK0IkpoItOYZbaSk663+NG0zBwxIpCSYK w37A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r16si1323139ejs.21.2020.10.29.01.58.44; Thu, 29 Oct 2020 01:59:06 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726743AbgJ2Cp0 (ORCPT + 99 others); Wed, 28 Oct 2020 22:45:26 -0400 Received: from mx2.suse.de ([195.135.220.15]:58232 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726233AbgJ1Vdn (ORCPT ); Wed, 28 Oct 2020 17:33:43 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 2D271AAB2; Wed, 28 Oct 2020 16:55:46 +0000 (UTC) Date: Wed, 28 Oct 2020 17:55:43 +0100 From: Joerg Roedel To: Arvind Sankar Cc: Joerg Roedel , Borislav Petkov , x86@kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Dave Hansen , Andy Lutomirski , Peter Zijlstra , Kees Cook , Martin Radev , Tom Lendacky , linux-kernel@vger.kernel.org Subject: Re: [PATCH v3 1/5] x86/boot/compressed/64: Introduce sev_status Message-ID: <20201028165543.GL22179@suse.de> References: <20201021123938.3696-1-joro@8bytes.org> <20201021123938.3696-2-joro@8bytes.org> <20201026182706.GG22116@zn.tnic> <20201028082352.GA18723@8bytes.org> <20201028165007.GB1989568@rani.riverdale.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201028165007.GB1989568@rani.riverdale.lan> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 28, 2020 at 12:50:07PM -0400, Arvind Sankar wrote: > On Wed, Oct 28, 2020 at 09:23:52AM +0100, Joerg Roedel wrote: > > On Mon, Oct 26, 2020 at 07:27:06PM +0100, Borislav Petkov wrote: > > > A couple of lines above you call get_sev_encryption_bit() which already > > > reads MSR_AMD64_SEV. Why not set sev_status there too instead of reading > > > that MSR again here? > > > > > > It can read that MSR once and use sev_status(%rip) from then on to avoid > > > reading that MSR multiple times... > > > > Right, makes sense. I updated the patch. > > Hang on, get_sev_encryption_bit() is also called from startup_32(), > so it can't contain any 64-bit instructions to set sev_status. Yeah, figured that out too and discussed it with Boris. Decided to leave it as-is and add a comment why the MSR is re-read. Thanks, Joerg