From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: [PATCH v3 54/75] x86/sev-es: Handle DR7 read/write events Date: Thu, 11 Jun 2020 15:06:33 +0200 Message-ID: <20200611130633.GD11924@8bytes.org> References: <20200428151725.31091-1-joro@8bytes.org> <20200428151725.31091-55-joro@8bytes.org> <20200525105935.GH25636@zn.tnic> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20200525105935.GH25636@zn.tnic> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: virtualization-bounces@lists.linux-foundation.org Sender: "Virtualization" To: Borislav Petkov Cc: Juergen Gross , Tom Lendacky , Dave Hansen , Mike Stunes , Kees Cook , kvm@vger.kernel.org, Peter Zijlstra , Cfir Cohen , x86@kernel.org, linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org, Joerg Roedel , Masami Hiramatsu , Andy Lutomirski , hpa@zytor.com, Erdem Aktas , David Rientjes , Dan Williams , Jiri Slaby List-Id: virtualization@lists.linuxfoundation.org On Mon, May 25, 2020 at 12:59:35PM +0200, Borislav Petkov wrote: > On Tue, Apr 28, 2020 at 05:17:04PM +0200, Joerg Roedel wrote: > > + if (data) > > + data->dr7 = val; > > Are we still returning ES_OK if !data? Yes, it just means we ignore DR7 writes when they happen early before runtime_data is allocated. Since the DR7 value never makes it to the hardware register anyway, it doesn't matter. Joerg