Received: by 10.223.164.202 with SMTP id h10csp428038wrb; Thu, 30 Nov 2017 01:31:46 -0800 (PST) X-Google-Smtp-Source: AGs4zMaCJo+wmyo3wxIwJGkM93JGUvpXxOharI3tZlhcnFva+1mK0yYR5+VBTq1VQHUcBffj1mTq X-Received: by 10.101.83.13 with SMTP id m13mr1769304pgq.151.1512034306116; Thu, 30 Nov 2017 01:31:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1512034306; cv=none; d=google.com; s=arc-20160816; b=K/ymxRyvZ5S4PkeJzTOg6qoFggGBA/kqJFT/AOxTWW+xNeqXV8if4OxX0bJN92CG/9 NKGhHJNMJ5zYCagmB5SYSGiO3dB/4Na/zkpO1vNBPK7lAFhGaJrDzmXy1HJwvwhUUy3V tMEzOmDEfJJN8de4ji5tiXTJUQsSdFdB65uKz+nhJxDDHkRRNE9JfuI+VdwPBY/ylvN+ 7bj8XZl/uPilMh/OyT0MTWAnLEQM6dvs46C9IZIGokHPRvkph1LHXr0rAQbxd6bd00rN u56VznYqOTINUlZ/tSEenIVRAFQ8B2Gxj1Qoe2Qx0MSYoyPd1aEiwnjc6d7DpcuWgiyh 9Kxg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=12x6n60JKd7ziu4GrxiLRlzCUBQqL4WM9Bp+ArAbNKk=; b=Cce7xVel1Fdae+fG5N8vFomS9dMThn7uUafAeyIHHWTwN3Q34Zyg0FgyQAdyFPpedc 9LqurtufQA2uSgUF7DEodqiJ7qDD0xovT62rcqGN1th71rIqjmmfQm6AhGCkSu1rk8BL TQixDV/B8U8eHULru5RCoH+Id6Yc0enRxV2byiMa/FSYd2QeZ6kjYIXUP5ZYDpJAlzQc u+NqoUw+8tT4gh6PmzFUIuTaKS4RCMuG+X9yp9eKJGNdv0eBiG1Ezyy1PzafaWEy7Woi t3X+WwhhHbkbKS0JJVkxfdnRqMgMkUzjwIur73gPxapetSnsGGfQsM6LziMpBPEOKIMi J9BQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=JFp/Uk8u; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h6si2746777pll.190.2017.11.30.01.31.32; Thu, 30 Nov 2017 01:31:46 -0800 (PST) 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=@gmail.com header.s=20161025 header.b=JFp/Uk8u; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751065AbdK3JaN (ORCPT + 99 others); Thu, 30 Nov 2017 04:30:13 -0500 Received: from mail-ua0-f174.google.com ([209.85.217.174]:42304 "EHLO mail-ua0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750798AbdK3JaJ (ORCPT ); Thu, 30 Nov 2017 04:30:09 -0500 Received: by mail-ua0-f174.google.com with SMTP id p33so5301605uag.9; Thu, 30 Nov 2017 01:30:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=12x6n60JKd7ziu4GrxiLRlzCUBQqL4WM9Bp+ArAbNKk=; b=JFp/Uk8uxYNCTTkC1vLbyGxbY3xAtmOwMsWF+2UxIMpiswtJ7MCQGBYsEu2to8N29Y 9oifQf69cuBfYwzrH5MKBmbHkugEZ7k39dMbfX3bdCPc4aqJ18F7pTiQ4S+u4TJCUEbi FWw/djeNcMyME06IdtIkXSJvPupRi94T4cutMi2NTuBtPn1QI5PPLXNPS2+4sWVFt/ma 8U48qSbpGMyFx2jR3iBefsUT4CQZA9blmvJYPQMSJYZPCzTPdCd3cyWgDn+p2CZyYELG mGzlJCs1O4Q/e1xPV+nPcnUfIyEVfFkG71Pcn65A/f6vs41N8Pu0eQoZ18u2azRid6KG 2s9Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=12x6n60JKd7ziu4GrxiLRlzCUBQqL4WM9Bp+ArAbNKk=; b=FdNXZC8Xog5X0aNKxIWTfXwQsTnCjrmM0xwwMe1v4cPF/089vM/rpFPTHMUydVivIL dsiqGNskFO57tf2ksLP7BTLTjjSESSbULmvX/R4AAggUS0Xfy+ED/hRSRW8q4QtHXWwR UGlL0SmnWrKMZ/3dPwYfPOa/lMiIHCvv8lrbrGiaTQOulyDCNIw7EDBizOd3r+gl+QN0 As9jN5rpb64pzrxhaKVcpC8zpHkVEZ9uYQSoiowdUvmOuJ9iTWwnIuFZXomyaSv3KSlv ohAxEOUA3fHRvO5sJ90wFUsppKaJIzdPvfMi2bb3tPTss24LqYUJQaMY40WmEFCur5DL sHPQ== X-Gm-Message-State: AKGB3mJx/3rWnSxAANR7rtqVKYGvDZ7DRyudkdgY5uOaS/hGVb0zIEqz RI9pM144ERO4k1EWiA6pYmAB3fpcft+FVYN2dAU= X-Received: by 10.176.0.73 with SMTP id 67mr1363641uai.132.1512034208158; Thu, 30 Nov 2017 01:30:08 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.27.105 with HTTP; Thu, 30 Nov 2017 01:29:27 -0800 (PST) In-Reply-To: References: <5e1be9ebc591c6de79b75f726a5a38b2564eaa92.1511785528.git.green.hu@gmail.com> From: Greentime Hu Date: Thu, 30 Nov 2017 17:29:27 +0800 Message-ID: Subject: Re: [PATCH v2 25/35] nds32: Build infrastructure To: Geert Uytterhoeven Cc: Arnd Bergmann , Greentime , Linux Kernel Mailing List , linux-arch , Thomas Gleixner , Jason Cooper , Marc Zyngier , Rob Herring , Networking , Vincent Chen , DTML , Al Viro , David Howells , Will Deacon , Daniel Lezcano , "linux-serial@vger.kernel.org" , Vincent Chen Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2017-11-30 15:52 GMT+08:00 Geert Uytterhoeven : > On Thu, Nov 30, 2017 at 6:48 AM, Greentime Hu wrote: >> 2017-11-30 4:27 GMT+08:00 Arnd Bergmann : >>> On Wed, Nov 29, 2017 at 3:10 PM, Greentime Hu wrote: >>>> 2017-11-29 19:57 GMT+08:00 Arnd Bergmann : >>>>> On Wed, Nov 29, 2017 at 12:39 PM, Greentime Hu wrote: >> I think I can use this name "CPU_V3" for all nds32 v3 compatible cpu. >> It will be implemented like this. >> >> config HWZOL >> bool "hardware zero overhead loop support" >> depends on CPU_D10 || CPU_D15 >> default n >> help >> A set of Zero-Overhead Loop mechanism is provided to reduce the >> instruction fetch and execution overhead of loop-control instructions. >> It will save 3 registers($LB, $LC, $LE) for context saving if say Y. >> You don't need to save these registers if you can make sure your user >> program doesn't use these registers. >> >> If unsure, say N. >> >> config CPU_CACHE_NONALIASING >> bool "Non-aliasing cache" >> depends on !CPU_N10 && !CPU_D10 >> default n >> help >> If this CPU is using VIPT data cache and its cache way size is larger >> than page size, say N. If it is using PIPT data cache, say Y. >> >> If unsure, say N. > > I still think it will be easier to revert the logic, and have > CPU_CACHE_ALIASING. > Thanks Geert I will implement it like this. config HWZOL bool "hardware zero overhead loop support" depends on CPU_D10 || CPU_D15 default n help A set of Zero-Overhead Loop mechanism is provided to reduce the instruction fetch and execution overhead of loop-control instructions. It will save 3 registers($LB, $LC, $LE) for context saving if say Y. You don't need to save these registers if you can make sure your user program doesn't use these registers. If unsure, say N. config CPU_CACHE_ALIASING bool "Aliasing cache" depends on CPU_N10 || CPU_D10 || CPU_N13 || CPU_V3 default y help If this CPU is using VIPT data cache and its cache way size is larger than page size, say Y. If it is using PIPT data cache, say N. If unsure, say Y. choice prompt "CPU type" default CPU_V3 config CPU_N15 bool "AndesCore N15" config CPU_N13 bool "AndesCore N13" select CPU_CACHE_ALIASING if ANDES_PAGE_SIZE_4KB config CPU_N10 bool "AndesCore N10" select CPU_CACHE_ALIASING config CPU_D15 bool "AndesCore D15" config CPU_D10 bool "AndesCore D10" select CPU_CACHE_ALIASING config CPU_V3 bool "AndesCore v3 compatible" select ANDES_PAGE_SIZE_8KB endchoice From 1585476753669767503@xxx Thu Nov 30 07:54:19 +0000 2017 X-GM-THRID: 1585224361841060243 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread