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.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_MUTT 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 5C224C282CE for ; Tue, 4 Jun 2019 14:35:00 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3D52124A3A for ; Tue, 4 Jun 2019 14:35:00 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727622AbfFDOe7 (ORCPT ); Tue, 4 Jun 2019 10:34:59 -0400 Received: from verein.lst.de ([213.95.11.211]:36757 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727470AbfFDOe7 (ORCPT ); Tue, 4 Jun 2019 10:34:59 -0400 Received: by newverein.lst.de (Postfix, from userid 2407) id B6BA368B05; Tue, 4 Jun 2019 16:34:32 +0200 (CEST) Date: Tue, 4 Jun 2019 16:34:32 +0200 From: Christoph Hellwig To: Peter Zijlstra Cc: Christoph Hellwig , x86@kernel.org, Sebastian Andrzej Siewior , linux-kernel@vger.kernel.org Subject: Re: [PATCH 2/3] x86/fpu: Simplify kernel_fpu_begin Message-ID: <20190604143432.GA24168@lst.de> References: <20190604071524.12835-1-hch@lst.de> <20190604071524.12835-3-hch@lst.de> <20190604114701.GM3402@hirez.programming.kicks-ass.net> <20190604131138.GB22542@lst.de> <20190604133417.GD3419@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190604133417.GD3419@hirez.programming.kicks-ass.net> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 04, 2019 at 03:34:17PM +0200, Peter Zijlstra wrote: > > Well, this is intended to not change semantics. If we should fix > > this is should be a separate patch before or after this series. > > Sure; it's just that I just noticed it. We've recently ran into a > similar issue elsewhere. Ok, I'll send a follow on.