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.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,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 8A5ABC04EB9 for ; Mon, 3 Dec 2018 22:08:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 50F4520851 for ; Mon, 3 Dec 2018 22:08:50 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=alien8.de header.i=@alien8.de header.b="YWoaeDuL" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 50F4520851 Authentication-Results: mail.kernel.org; dmarc=fail (p=reject dis=none) header.from=alien8.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725996AbeLCWIt (ORCPT ); Mon, 3 Dec 2018 17:08:49 -0500 Received: from mail.skyhub.de ([5.9.137.197]:58606 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725903AbeLCWIs (ORCPT ); Mon, 3 Dec 2018 17:08:48 -0500 Received: from zn.tnic (p200300EC2BC7BF00329C23FFFEA6A903.dip0.t-ipconnect.de [IPv6:2003:ec:2bc7:bf00:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id B1E291EC02AE; Mon, 3 Dec 2018 23:08:46 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1543874926; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=Uc8VYgqal0W5LWwMwovtyq2uyvTU7nfLcLuMNm8VR24=; b=YWoaeDuLH8B7poKqkM3Koe2gplliCAITpYBuEE6nDAjirA/sfD9c+j7AzHD1r1EvDUoLsj oecTm9oIRZpAc0oPjLFGBTh/h9gAxoFAYJKAcadckyAbG4mhKo1mA//tOsGXs7jILgAvBf zeLx4QTP7ECwWNM0mlDGTZR6bTJAtK8= Date: Mon, 3 Dec 2018 23:08:41 +0100 From: Borislav Petkov To: Ard Biesheuvel , Sebastian Andrzej Siewior Cc: Dave Hansen , Ingo Molnar , the arch/x86 maintainers , nstange@suse.de, Rik van Riel , KVM devel mailing list , "Jason A. Donenfeld" , Linux Kernel Mailing List , Ingo Molnar , Radim =?utf-8?B?S3LEjW3DocWZ?= , "H. Peter Anvin" , Thomas Gleixner , Andy Lutomirski , Borislav Petkov , linux-efi , Paolo Bonzini , linux-tip-commits@vger.kernel.org Subject: Re: [tip:x86/fpu] x86/fpu: Don't export __kernel_fpu_{begin,end}() Message-ID: <20181203220841.GB4794@zn.tnic> References: <20181129150210.2k4mawt37ow6c2vq@linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 03, 2018 at 10:12:19PM +0100, Ard Biesheuvel wrote: > > + * Using the FPU in hardirq is not allowed. > > According to the documentation in x86/kernel/fpu/core.c, this is not > true. So which one is accurate? I think you mean the irq from user mode... Yap, we do allow that. Sebastian? Thx. -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.