Received: by 2002:a05:6a10:1d13:0:0:0:0 with SMTP id pp19csp3256617pxb; Sun, 29 Aug 2021 19:35:57 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyn67Itejh0wM5H0Ha8b2TRJN5p5NCVFdsYidMcWuz3s72E30f7F4+ybZSMzlX1o9+MAQ44 X-Received: by 2002:a17:906:a044:: with SMTP id bg4mr22901008ejb.312.1630290957225; Sun, 29 Aug 2021 19:35:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1630290957; cv=none; d=google.com; s=arc-20160816; b=kcp9nDKBa1aMWuEPie8UIacvmAIH3LwijTc/jUtMmyjw4eqiiGTn5iwu/3/TQmHdq3 cPBC/gLxtpGBRKn+I3QS1e5qoUCzLUIcRKLn68zGd/BcEdWms+HGnfeqV+PhX5i+0LJq s41LhWHsd81ZrmNrTlLdzG4z9a/0tFSeQtD+EKpRoJzEpi0o22bPPTsTyw2KhXP/8yrU 3hyxrst1bG3K1Hgcp2PGLeRzIxs/JgrtQsUIT3aSi8xsjsNNhRTAfko7ushjx1nCIYoK I76x2/qFIx/9KfjKilb+Hrm8jGAK/5Z/3PQ1Pag2TBUt8SrinCouMlbwv22MGQXXw7aI 5Gkg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject:dkim-signature:dkim-signature; bh=v3f6jPzzBipbSiu4aVjPCilgneHFN9knpU6Krm+kjSo=; b=DlpcLy2sAHnxOjarR+hwEZ0QeiuaUFguekKlaybzekzdsOzM+3KyKmD71ipyR4RFBX I7jZ6+Dxrt5hdh3koShJKAbw2aekI6OGG1q+AXdLMbKsWS+vIN4ZKgnXopN+D+rjuVYU MgQdRsBHEf/gwd57g4/pGqO8wQJMKdkIHYtvV8ct0l/XV0SNdakQC8E9KGquiv3E4WsO Cq4CkDVO20pS2Ok7nUrJAqwnvthwhD9zTeMqQlZ1/Rv6ZBHjV/O8RwqB15aMEaWaOCj4 iCCBS7rFN6k/82GqUn5uKPIM+gOesp9kmRbwzwZG125U1OFbl52fMRG6pjZamZz7LtGS tehw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@flygoat.com header.s=fm3 header.b=tukNWEta; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=mKgrGGxu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m24si13403535ejd.38.2021.08.29.19.35.34; Sun, 29 Aug 2021 19:35:57 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@flygoat.com header.s=fm3 header.b=tukNWEta; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b=mKgrGGxu; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235012AbhH3CdM (ORCPT + 99 others); Sun, 29 Aug 2021 22:33:12 -0400 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:41629 "EHLO out3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234922AbhH3CdF (ORCPT ); Sun, 29 Aug 2021 22:33:05 -0400 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 480C75C0085; Sun, 29 Aug 2021 22:32:11 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Sun, 29 Aug 2021 22:32:11 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=flygoat.com; h= subject:to:cc:references:from:message-id:date:mime-version :in-reply-to:content-type:content-transfer-encoding; s=fm3; bh=v 3f6jPzzBipbSiu4aVjPCilgneHFN9knpU6Krm+kjSo=; b=tukNWEtaWbA8o+Fjz FoTU9WTAqtl2aDhMVPweMspb92x2AlreH5LSTg8iJN5YLfoIlDblsGUofdVYDvVz XauQMF0uRCc6kE+vTamf3BtXFze8AQw+XznflsYBM2ueCu/n2f0Bi+C6VLYCq/l2 rDsOy7WHsGPRf/+mcInGiZo+cnAyIt4nVZy3XfN3EL3LevaK1A39cPaP5TgauLu9 CBUfGGFLJq2e/BuuOEgcmGgOviuGds0tCuJE/G2fZpCrQrYYzn8UFvEjju6KwMiM 0iiby2ffzWQKaAE56bJc07e9tl16j5kvj5ejmHyXIxaDkqUO1p7zoWfYwkdRGzGq WHR+Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=v3f6jPzzBipbSiu4aVjPCilgneHFN9knpU6Krm+kj So=; b=mKgrGGxuRadgm9g6e3ZPiruUZ41o5lpZ+PtBW5zNm1ccFwPTBCFM2GYf3 gk0cRqaKiH91FUhB48UQmPvIyovsAD9JAk1BOROjYgx9CqPRdIrMi6QDX7MASCxH 4ha/OyaH5eyyiPWz6tPkkxw3kJhU7H7UoEKpCxt1WaebJXk6QVw8uk68vyus1AnJ 6wffj5vSS7WNq+wt6vR+YTXBBaFg6HKURcaP2/yb+ZKoVOSOWsQhp27A1x/Y1jZx 1jvh3sar4NYFCzm1cZHb+S3gry7TYpI/+1waZQP2rwNHJtBSChWR0+JTlwvHIREk iTmidX0fGY5PypyO40ibPrC3YCm4A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvtddruddukedgiedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepuffvfhfhkffffgggjggtgfesthekredttdefjeenucfhrhhomheplfhirgig uhhnucgjrghnghcuoehjihgrgihunhdrhigrnhhgsehflhihghhorghtrdgtohhmqeenuc ggtffrrghtthgvrhhnpeeihffghfeikedugeejvefgffevgeevgeehfffhudeiieffffev ffeugeevfefgfeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehjihgrgihunhdrhigrnhhgsehflhihghhorghtrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 29 Aug 2021 22:32:07 -0400 (EDT) Subject: Re: [PATCH] mips: remove reference to "newer Loongson-3" To: Xi Ruoyao , linux-mips@vger.kernel.org Cc: Thomas Bogendoerfer , linux-kernel@vger.kernel.org, Huacai Chen References: <0b7c9431efb12c2d957fcc53ec8f0743725d61b3.camel@mengyan1223.wang> From: Jiaxun Yang Message-ID: Date: Mon, 30 Aug 2021 10:32:03 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: <0b7c9431efb12c2d957fcc53ec8f0743725d61b3.camel@mengyan1223.wang> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 在 2021/8/29 20:49, Xi Ruoyao 写道: > Newest Loongson-3 processors have moved to use LoongArch architecture. > Sadly, the LL/SC issue is still existing on both latest Loongson-3 > processors using MIPS64 (Loongson-3A4000) and LoongArch > (Loongson-3A5000). LLSC is fixed on Loongson-3A4000 as per CPUCFG report. > > As it's very unlikely there will be new Loongson-3 processors using > MIPS64, let's stop people from false hoping. > > Signed-off-by: Xi Ruoyao > Cc: Huacai Chen > --- > > Huacai: how's the status of LL/SC issue on Loongson-2K? If > the issue exists on it as well, we can just force > CPU_LOONGSON3_WORKAROUNDS when CONFIG_CPU_LOONGSON64 and > CONFIG_SMP are both selected. Loongson-2K do need LLSC workaround, although the reason behind the workaround seems different... Thanks. - Jiaxun > > arch/mips/Kconfig | 9 ++------- > 1 file changed, 2 insertions(+), 7 deletions(-) > > diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig > index 6dfb27d531dd..ff5f344a371e 100644 > --- a/arch/mips/Kconfig > +++ b/arch/mips/Kconfig > @@ -1433,19 +1433,14 @@ config LOONGSON3_ENHANCEMENT > new Loongson-3 machines only, please say 'Y' here. > > config CPU_LOONGSON3_WORKAROUNDS > - bool "Old Loongson-3 LLSC Workarounds" > + bool "Loongson-3 LLSC Workarounds" > default y if SMP > depends on CPU_LOONGSON64 > help > Loongson-3 processors have the llsc issues which require workarounds. > Without workarounds the system may hang unexpectedly. > > - Newer Loongson-3 will fix these issues and no workarounds are needed. > - The workarounds have no significant side effect on them but may > - decrease the performance of the system so this option should be > - disabled unless the kernel is intended to be run on old systems. > - > - If unsure, please say Y. > + Say Y, unless you know what you are doing. > > config CPU_LOONGSON3_CPUCFG_EMULATION > bool "Emulate the CPUCFG instruction on older Loongson cores"