Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp4399716imm; Mon, 20 Aug 2018 15:24:20 -0700 (PDT) X-Google-Smtp-Source: AA+uWPxQe0ljJGT6SkdpUVyRW0DAx3WlTSL0h891z2lJGy7qz6/p3UTJxXoFR8HSh+ZoaO7Jav+g X-Received: by 2002:a62:591a:: with SMTP id n26-v6mr50369350pfb.94.1534803860504; Mon, 20 Aug 2018 15:24:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534803860; cv=none; d=google.com; s=arc-20160816; b=nk+++Y/lSnmoPpvVR8Gk0RDgZ8L2xe5QRm8sf95JEKmGz4ZM2CeLCyGR9lLl9AjNzR QPa/PHIcO37K6E5huIap/8FYwAOAFPTb+kxQzlZMtfI9OaaGIeQutz+YwxBgQHzYIEDl qw+78T+DGsvdI+g4ikwyn98hV2rMKn35VzsBO/QEfy331pEMIMvcwB0Fj2GPG6tU7n6d 2Y0jiGxHYx6WmLW7aCCJgiSfAVPo2Ux+cUDOHHhmWXmMXUDLDoaaqmZ0F0MMApOZBBo7 egh+42+KHuWGQtTuj3ny6xNwfpSWSC5YLAesjsbu/X0Dzh6HDWl2bjtG0eW2muQRPscP NxKA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:to:from:cc:in-reply-to:subject:date:dkim-signature :arc-authentication-results; bh=zmdehfLIL6FBOxM84ul/2UsCLpTP9eAPq9bQfBkObjw=; b=pu1frWmVPvWtPWwpTd/8B3PMMZIhPLJzPEjGPhHPI3lVUtBBPgoQ2OebN2CNjrueN1 iMBCgmVtrrG84kClyhMpSDAaCIpgPNVPqLcNvaDD5DJ0XfGeKQ7NKRg4H8842DgBIvmf cRp09d86QkR4xuHJJZdLqdsrrRMD6qkpporCJv/xSI8hZq88i9TP6+13uHOJPd1dJlAi BMxtzI7cSb7+7ArGg3G1DvuSFfzLQf+aJaRYGwkq7ZHR6WbMA3a75Zy1FZG0X068mSb6 lotgjHpIsxrAFduOYXhYMQBicH/qwcpWmXf9Xd/RwGrDPpRle8WFHfiLXQcs7cO3JP3R Ow5A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sifive.com header.s=google header.b=ntqzUw+t; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l11-v6si461727pls.245.2018.08.20.15.24.05; Mon, 20 Aug 2018 15:24:20 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@sifive.com header.s=google header.b=ntqzUw+t; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726683AbeHUBk0 (ORCPT + 99 others); Mon, 20 Aug 2018 21:40:26 -0400 Received: from mail-pl0-f67.google.com ([209.85.160.67]:44724 "EHLO mail-pl0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726119AbeHUBkZ (ORCPT ); Mon, 20 Aug 2018 21:40:25 -0400 Received: by mail-pl0-f67.google.com with SMTP id ba4-v6so7784752plb.11 for ; Mon, 20 Aug 2018 15:22:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=date:subject:in-reply-to:cc:from:to:message-id:mime-version :content-transfer-encoding; bh=zmdehfLIL6FBOxM84ul/2UsCLpTP9eAPq9bQfBkObjw=; b=ntqzUw+tYW6l7GBXWV2Axs9aTzSJb+efmTXyJK2G9YwcGIs/vgm6Px9XvLLd58RQ57 Jj/RKqMEp5VEPf0MMIBrR+JMIeXdbm0M4/hZr3HSbeFXsIgpZzQo0VpuFjDJemtqRtHS 7jf0NTYypwi1ZOPzekvjKN9hDy3CFLAwX9GE6W3M8VHzDt9W4urWjlWUoVqhUTZ8Qlcr wbelBeMFun4nswYrtduPW35kccq9T+tKEGF0mwrPaY+6gPTbLcxnDJFlT4iKvd38IJTJ EnC81Z+8LwALZEfszRRRtnw7aGwDTxDSkiYxD3Fqw6yII0oJWt4e1YXvSz4Ba2WZxpLJ 8eSQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:subject:in-reply-to:cc:from:to:message-id :mime-version:content-transfer-encoding; bh=zmdehfLIL6FBOxM84ul/2UsCLpTP9eAPq9bQfBkObjw=; b=rfQ3BArvKCP9QpZBUXTS7X0nW9oXGBajUl4cxrdHsgi7IVKzV0opK9d91U/cw9ZcYu vetwTQhjY5MEty1sE8sAsrlBVu8xbEH+L+2b41oFs5Y+xME+2wiCuReVHZyMDGmSNyij nlQh26aXLSBY3SHjXgYU2tgWvr9t+RRN45jyy5TQ/aAB1f/fGcHZnzx4fdVzSbJ29Wcq AEmR/HiHEFdJglTjwon00m7wyT88JNASPe34Q88uZ26/YkvwLsfZ6btVBpIhncQZmDPi gG65D8OZbFjR/mVM6mLW2heBgZuBEOC8tg0FcQamw7rWmvuPuTj08AE8+OuxgJ5cPPBM 2elw== X-Gm-Message-State: AOUpUlEM+NovASCBMLccDXWGs+drs/ZQ84zUylF46FbF0jlVwXbuVTjt 35nr/927XB6sHelFwT6soid00QIlFM0= X-Received: by 2002:a17:902:760b:: with SMTP id k11-v6mr11374103pll.185.1534803778863; Mon, 20 Aug 2018 15:22:58 -0700 (PDT) Received: from localhost ([12.206.222.5]) by smtp.gmail.com with ESMTPSA id l3-v6sm13221728pff.8.2018.08.20.15.22.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Aug 2018 15:22:57 -0700 (PDT) Date: Mon, 20 Aug 2018 15:22:57 -0700 (PDT) X-Google-Original-Date: Mon, 20 Aug 2018 15:16:46 PDT (-0700) Subject: Re: [PATCH v4 0/5] riscv: Add support to no-FPU systems In-Reply-To: <1533698685-18022-1-git-send-email-alankao@andestech.com> CC: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org, albert@sifive.com, Christoph Hellwig , Andrew Waterman , Arnd Bergmann , Darius Rad , alankao@andestech.com From: Palmer Dabbelt To: alankao@andestech.com Message-ID: Mime-Version: 1.0 (MHng) Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 07 Aug 2018 20:24:40 PDT (-0700), alankao@andestech.com wrote: > This patchset adds an option, CONFIG_FPU, to enable/disable floating- > point procedures. > > Kernel's new behavior will be as follows: > > * with CONFIG_FPU=y > All FPU codes are reserved. If no FPU is found during booting, a > global flag will be set, and those functions will be bypassed with > condition check to that flag. > > * with CONFIG_FPU=n > No floating-point instructions in kernel and all related settings > are excluded. > > Changes in v4: > - Append a new patch to detect existence of FPU and followups. > - Add SPDX header to newly created fpu.S. > - Fix a build error, sorry for that. > - Fix wording, style, etc. > > Changes in v3: > - Refactor the whole patch into independent ones. > > Changes in v2: > - Various code cleanups and style fixes. > > Alan Kao (5): > Extract FPU context operations from entry.S > Refactor FPU code in signal setup/return procedures > Cleanup ISA string setting > Allow to disable FPU support > Auto-detect whether a FPU exists > > arch/riscv/Kconfig | 9 +++ > arch/riscv/Makefile | 19 +++--- > arch/riscv/include/asm/hwcap.h | 3 + > arch/riscv/include/asm/switch_to.h | 21 ++++++ > arch/riscv/kernel/Makefile | 1 + > arch/riscv/kernel/cpufeature.c | 11 +++ > arch/riscv/kernel/entry.S | 87 ----------------------- > arch/riscv/kernel/fpu.S | 106 +++++++++++++++++++++++++++++ > arch/riscv/kernel/process.c | 4 +- > arch/riscv/kernel/signal.c | 79 +++++++++++++-------- > 10 files changed, 214 insertions(+), 126 deletions(-) > create mode 100644 arch/riscv/kernel/fpu.S Aside from the CFLAGS issue this looks good. I've queued this up in kernel.org/palmer/linux.git/next-nofpu, but I'm not going to put this on for-next until after the merge window closes. Thanks!