Received: by 10.223.164.202 with SMTP id h10csp4308744wrb; Wed, 29 Nov 2017 04:28:00 -0800 (PST) X-Google-Smtp-Source: AGs4zMYIUfoSGY9EOBDNGBBJqbY8Rs7YlgVo5h8XsHVhfDc49pBNHXz88CGPVlD1/bCNVnQ9SXQg X-Received: by 10.159.252.1 with SMTP id n1mr2688007pls.415.1511958480454; Wed, 29 Nov 2017 04:28:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1511958480; cv=none; d=google.com; s=arc-20160816; b=N/aHZ1sBNoQG5tzNbnP7edsrlqhilvUkwmfYA0TKAlLiiax2JlraWrVnC3siGpUs5z bXEcjA+GRqq0bz5AIZgQJK045cUPDb7kbG5iPNK4z0vQZWpLhk7H7v0SQBvgEb60902f x4MNaCOMqUWKhquROWXH6en9fedv0wD4nU+3Pp8P8rOa7DAPU13sCUco4kKkyWt0r9Lf xkzJV/JTj4zJO5CtU8JVmHTU+L/2Wy87WGhuo+Hel2DEUmtrGNqS8LIrjHaUUpMi4fTv 87RnVuIt5VFCLUzwNdCCUdoN77AD1M40zUzbHJCqm8YHGYIAREyV0hwd7GM9ZIxI2Q68 9JZA== 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=rvakqsEgwbyhSdnlE+i48jmyK/N8HD49q7hTwfc/BWA=; b=HPbOgaY90cEpBxP9Of/9nEFXiP+Iqz2pEw0k1iJHOEgcLxJ38FM+8tW66AoMsVK8SC /cdKX3D6p0+G/r6aUeDVM4iEQYktT2HXwwAisv7sw9og3XBmfHqPSfOP2cgKB9pkThIt rSJbxY3KkeRrfqMuO3gbDqg/9PTTy5owvEG7+BEI7mWMC20InlFFQBtjOgiECMAuCNQ/ Endj8qdJk4UqOTYStB2C6zq2+pfgx27Jh/1Xhpbl0KjFyDdiQwTOib9XQazKq7gPlrIn UF/e8JLNrworLI0TmrVvBYxviFkNoBhd/IAzLo4Az6DrAx8jfdPf06OKCBaC1ucIQGM7 4xdQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=UpE4zYwd; 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 l3si1175831pgr.804.2017.11.29.04.27.49; Wed, 29 Nov 2017 04:28:00 -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=UpE4zYwd; 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 S932093AbdK2Ikf (ORCPT + 71 others); Wed, 29 Nov 2017 03:40:35 -0500 Received: from mail-vk0-f67.google.com ([209.85.213.67]:39541 "EHLO mail-vk0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932065AbdK2Ikc (ORCPT ); Wed, 29 Nov 2017 03:40:32 -0500 Received: by mail-vk0-f67.google.com with SMTP id h203so707281vka.6; Wed, 29 Nov 2017 00:40:31 -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=rvakqsEgwbyhSdnlE+i48jmyK/N8HD49q7hTwfc/BWA=; b=UpE4zYwdctSvXZtiZcz44TOG2Nfq/u4SG41NohDpWlN8Z0tQ5pZINKaP/Z3R11Gf/F sFoUSoFgt2K/xFYiBxTzYbNdnBsmTorLXZPQlDAqAi4BNn/Qp7L2MtCGb386V7vIxQJX MtlhOBFV3XO3Gge/CTs/aW61va4sJ9pElBEhRmKcG9V2apysRItuMnEMmDzLdEhTQ2ab wek41rqS8l2AI/UQhWNou+fWz2ykZH6zYK7zOZED+O0bm5illMI86HF2nE8WaIBeIaja 78SMaRHJGhniezzANyXbnicAjutyeNYjkvzin9cS5JmYhhr9g4WFsNpJtWBHT3jDi8gS z6sw== 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=rvakqsEgwbyhSdnlE+i48jmyK/N8HD49q7hTwfc/BWA=; b=M/ws2Fb/6p1jX3aeDevPDRmJyCGieIrYVnAoR59LaCRhTUVWWg1NfWpgnDvuf/HEPt ifeNpCjnQq+Rcw5yWFNVLSwLXpY3E9vgyRQDs4B+YrKH37Xq16uG1rcA4SFsRqt3xW/+ gwMaIGWJI1rwqrfRAfCcanfV8jGtWDiiC0+JVypowxB99LnTRBUySZs90S/Z/31km9zr pjUJZWjZISH9PBVZlPksZ48KupWM1YkSDBr9yL8AZdZ9WJQsV9upSkwSY94WHzThYFjR DqBalpwOqt+uGFG/NWw0gJvH4xEqK3jkxqu0wfnVQqMbr1OOKVn/7UKgLzk5Ynh1Jz9t xqlw== X-Gm-Message-State: AJaThX4w99onH4LKP/Ji/vXpxl3fS7OhtP9UoPOF9OgkRdgUy36JvC3V 6yw6cZPSAtJHrF0Cz7/Hyo0lgA+3kE/BFyt0NRY= X-Received: by 10.31.205.131 with SMTP id d125mr1652342vkg.198.1511944831446; Wed, 29 Nov 2017 00:40:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.27.105 with HTTP; Wed, 29 Nov 2017 00:39:51 -0800 (PST) In-Reply-To: References: <5e1be9ebc591c6de79b75f726a5a38b2564eaa92.1511785528.git.green.hu@gmail.com> From: Greentime Hu Date: Wed, 29 Nov 2017 16:39:51 +0800 Message-ID: Subject: Re: [PATCH v2 25/35] nds32: Build infrastructure To: Arnd Bergmann Cc: 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-27 22:21 GMT+08:00 Arnd Bergmann : > On Mon, Nov 27, 2017 at 1:28 PM, Greentime Hu wrote: > >> diff --git a/arch/nds32/Kconfig.cpu b/arch/nds32/Kconfig.cpu >> new file mode 100644 >> index 0000000..6b4013f >> --- /dev/null >> +++ b/arch/nds32/Kconfig.cpu >> @@ -0,0 +1,131 @@ >> +comment "Processor Features" >> + >> +config CPU_BIG_ENDIAN >> + bool "Big endian" >> + def_bool n >> + >> +config CPU_LITTLE_ENDIAN >> + bool "Little endian" >> + def_bool y > > These must be mutually exclusive, you surely get some build error if you try to > set both here. > > You can either make it a 'choice' statement to pick between the two, or you > can make CPU_LITTLE_ENDIAN a silent option like > > config CPU_BIG_ENDIAN > bool "Big endian" > > config CPU_LITTLE_ENDIAN > def_bool !CPU_BIG_ENDIAN > Thanks. I will fix it in the next version patch. >> +config CPU_CACHE_NONALIASING >> + bool "Non-aliasing cache" >> + 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 Y. > > Can you determine this from the CPU type? There is no cpu register to determine it. It also depeneds on page size and way size however page size is configurable by software. These codes are determined at compile time will be benefit to code size and performance. IMHO, I think it would be better to be determined here. >> +choice >> + prompt "Memory split" >> + depends on MMU >> + default VMSPLIT_3G >> + help >> + Select the desired split between kernel and user memory. >> + >> + If you are not absolutely sure what you are doing, leave this >> + option alone! >> + >> + config VMSPLIT_3G >> + bool "3G/1G user/kernel split" >> + config VMSPLIT_3G_OPT >> + bool "3G/1G user/kernel split (for full 1G low memory)" >> + config VMSPLIT_2G >> + bool "2G/2G user/kernel split" >> + config VMSPLIT_1G >> + bool "1G/3G user/kernel split" >> +endchoice > > I think you mentioned that the 1GB configuration is quite common, how > about making VMSPLIT_3G_OPT the default here? We use 1GB in our fpga platform, but I am not sure our customer's config and their user space program may use bigger memory space. Anyway, we will discuss it to decide the default value. Thanks for your suggestion. From 1585401539271424599@xxx Wed Nov 29 11:58:49 +0000 2017 X-GM-THRID: 1585224361841060243 X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread