From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Hansen Subject: Re: [PATCH 05/22] x86/fpu: Remove fpu->initialized usage in copy_fpstate_to_sigframe() Date: Fri, 18 Jan 2019 13:43:17 -0800 Message-ID: References: <20190109114744.10936-1-bigeasy@linutronix.de> <20190109114744.10936-6-bigeasy@linutronix.de> <20190116193603.GK15409@zn.tnic> <20190116224037.xkfnevzkwrck5dtt@linutronix.de> <20190117122253.GC5023@zn.tnic> <20190118211401.4komqsnvuof7563p@linutronix.de> <33f0e144-1eec-b1a1-8858-58f20d5e477d@intel.com> <20190118213717.fkbj5jmcdok7dbmb@linutronix.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Borislav Petkov , Ingo Molnar , Oleg Nesterov , linux-kernel@vger.kernel.org, x86@kernel.org, Andy Lutomirski , Paolo Bonzini , =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , kvm@vger.kernel.org, "Jason A. Donenfeld" , Rik van Riel , Dave Hansen To: Sebastian Andrzej Siewior Return-path: In-Reply-To: <20190118213717.fkbj5jmcdok7dbmb@linutronix.de> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 1/18/19 1:37 PM, Sebastian Andrzej Siewior wrote: > On 2019-01-18 13:17:28 [-0800], Dave Hansen wrote: >> On 1/18/19 1:14 PM, Sebastian Andrzej Siewior wrote: >>> The kernel saves task's FPU registers on user's signal stack before >>> entering the signal handler. Can we avoid that and have in-kernel memory >>> for that? Does someone rely on the FPU registers from the task in the >>> signal handler? >> >> This is part of our ABI for *sure*. > > I missed that part. I will try to look it up and look see if says > something about optional part. > But ABI means we must keep doing it even if there are no users? I'd bet a large sum of money there are users. Google for 'uc_mcontext fpregs'.