From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_NEOMUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 82B69C004C9 for ; Tue, 7 May 2019 21:59:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 482B5206A3 for ; Tue, 7 May 2019 21:59:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726415AbfEGV7c (ORCPT ); Tue, 7 May 2019 17:59:32 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:44248 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725843AbfEGV7b (ORCPT ); Tue, 7 May 2019 17:59:31 -0400 Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1hO87S-0005DA-7l; Tue, 07 May 2019 23:59:26 +0200 Date: Tue, 7 May 2019 23:59:26 +0200 From: Sebastian Andrzej Siewior To: Linus Torvalds Cc: Borislav Petkov , Rik van Riel , x86-ml , lkml Subject: Re: [GIT PULL] x86 FPU changes for 5.2 Message-ID: <20190507215925.3wfs7mia5aesedr2@linutronix.de> References: <20190507132632.GB26655@zn.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019-05-07 10:35:25 [-0700], Linus Torvalds wrote: > Has this gone through lots of testing, particularly with things like > FP signal handling and old machines that don't necessarily have > anything but the most basic FP state (ie Pentium class etc)? I tried it in qemu with incremental FPU capabilities so it went through all the possible load/restore variants during signal handling. I had a testcase which did SHA1 computation and a received a SIGALRM every second. This caught some bugs, most of them were xsave/xsaves related once the SHA1 result did not match. I tried something similar one the 8087 FPU. I had the series in the v5.0-RT tree which resulted in the most recent patch in that branch. > Linus Sebastian