From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Andrzej Siewior Subject: Re: [PATCH 14/22] x86/fpu: Eager switch PKRU state Date: Thu, 21 Mar 2019 18:10:05 +0100 Message-ID: <20190321171005.l3sywcudjvxmi27n@linutronix.de> References: <20190221115020.12385-1-bigeasy@linutronix.de> <20190221115020.12385-15-bigeasy@linutronix.de> <20190308180849.hy22jejhffp4n6uh@linutronix.de> <20190311110605.2xxjx2ym3n63lpr2@linutronix.de> <20190311143049.hclnlciq4rzqrtp6@linutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: linux-kernel@vger.kernel.org, x86@kernel.org, Andy Lutomirski , Paolo Bonzini , Radim =?utf-8?B?S3LEjW3DocWZ?= , kvm@vger.kernel.org, "Jason A. Donenfeld" , Rik van Riel , Dave Hansen To: Dave Hansen Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 2019-03-12 17:06:18 [-0700], Dave Hansen wrote: > Thanks for doing this. I'll see if I can dig into the test case and > figure out why it's not doing what I expected. It might be that the CPU > _could_ go back to the init state but chooses not to, or that something > else is taking us out of the init state before we reach the kernel code > in question. I'm going to drop that WARN_ON() check. The reason is that we are fully preemptible during fpstate_init() and a context switch during memset() and fpstate_init_xstate() triggers this warning. Sebastian