From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A396F34BA5B for ; Thu, 6 Aug 2026 16:34:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786034068; cv=none; b=Q3jvOtp00NkCsHYqGLEmlOpZ9fvzrzHorasWlMhOnhqvHqSY9nEEyowEOaeuAhf9CMiI26eNtzxaYlQFJGI3J+kwAl431sAPcZ7Cl8AFVwfhqTF4+1GyqlBEhkuZCJfygfNxlsaBSeQLb3StaY/Hum+BzysqES45w6QJWoBduTo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786034068; c=relaxed/simple; bh=bgE2aiW5ioHsmq40MJTtkyupGEyqCmca621fgCZEOBg=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References: MIME-Version:Content-Type; b=eJKmHepjnLHD12c+F1HHKRMbQrT9S/JOgTR6nXL2aDFD53hhVUlG0fZyuYc5x49A5G4ju4yETQvo534F8ZVoRY5KIkF8F3ZVFOU2crAQDNGHwcQnCGRO7uQxFbSBenkpV/f/QuBkqT/CxK7jRdJuL7afDFr3ZtzM97uyMaHUL/M= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=LSLYoLCF; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="LSLYoLCF" Received: by smtp.kernel.org (Postfix) with ESMTPSA id CCA071F000E9; Thu, 6 Aug 2026 16:34:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1786034067; bh=vPCPaGW6m03Dz8rTY9uUJofYQcJnNc0xegcWF4cgfhQ=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=LSLYoLCFi80c3Q4+oBR8MkzzcWUDZ5JfPhtRG3ODlWGMEGfp5/Dg0OExZAYI8CnOQ niEbf8nuwHyrrcgnAqDZctPO069pW8vATfVhr/+Mppmk1RA2tj8A3D1Uu+674Su8A3 4YAgWE6PT2xKvyMttejg3Rg8Ehtsn92KNdnKrbr8KOqSTDIt+xlNW0Lxo3+DZewSUH 3+arLdU//CiJNsCEdNYI84Ye+EulgyFjkP9RSb/heUmTx5rlxr6LbyiqlWdAJOZhMk AAfezMD26qT4VenU/wz+OPce7zEVWnsHqyPezj3hsmuuYTt/xH4eKazqNPVm7bxE7L 4h5ZE2NPJ0RBw== Date: Thu, 6 Aug 2026 10:34:23 -0600 (MDT) From: Paul Walmsley To: Vivian Wang cc: Paul Walmsley , Palmer Dabbelt , Alexandre Ghiti , Nam Cao , linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] riscv: cmpxchg: Use .option arch for Zacas and Zabha In-Reply-To: <20260717-riscv-no-zacas-zabha-in-march-v1-1-82b5b0799fb6@iscas.ac.cn> Message-ID: References: <20260717-riscv-no-zacas-zabha-in-march-v1-1-82b5b0799fb6@iscas.ac.cn> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII On Fri, 17 Jul 2026, Vivian Wang wrote: > Instead of adding these to -march globally, use .option arch to use > instructions from these extensions only in code paths where we know they > are available, like how it is done for most other extensions. > TOOLCHAIN_HAS_{ZACAS,ZABHA} already depend on AS_HAS_OPTION_ARCH, so > this is not a functionality regression even on older assemblers. > > Although the compiler is unlikely to generate atomics on its own accord, > this aligns handling of Zacas and Zabha with most other extensions and > improves consistency on how assembly code requiring extra extensions is > written in kernel code. > > This is analogous to the use of __LSE_PREAMBLE or .arch_extension lse in > arm64 code. > > Signed-off-by: Vivian Wang Thanks, queued for v7.3. - Paul