From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 72D61C433FE for ; Thu, 24 Nov 2022 09:19:24 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id EF7A26B0074; Thu, 24 Nov 2022 04:19:23 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id EA7056B0075; Thu, 24 Nov 2022 04:19:23 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D95506B0078; Thu, 24 Nov 2022 04:19:23 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id C91E26B0074 for ; Thu, 24 Nov 2022 04:19:23 -0500 (EST) Received: from smtpin02.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay04.hostedemail.com (Postfix) with ESMTP id 8E8F71A0A7A for ; Thu, 24 Nov 2022 09:19:23 +0000 (UTC) X-FDA: 80167787406.02.A1BEEAE Received: from mail-wm1-f53.google.com (mail-wm1-f53.google.com [209.85.128.53]) by imf06.hostedemail.com (Postfix) with ESMTP id 21623180007 for ; Thu, 24 Nov 2022 09:19:21 +0000 (UTC) Received: by mail-wm1-f53.google.com with SMTP id p13-20020a05600c468d00b003cf8859ed1bso796852wmo.1 for ; Thu, 24 Nov 2022 01:19:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rivosinc-com.20210112.gappssmtp.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=21RtI83U3AWt3cyeCJ2XmHc2ruDDyw09Go561vbFieg=; b=7q/OaKPtQ4IeYxQHQaC4aOn7zrvJ3Yr8RQyWvwQwcRu0jouQ1mzKgLwVH1+4CtBlT0 WqqJ97pJd1e6ipFHKwm0vRnNnfYpGlLhc2UVYB6Y3U09PlrX4FMMxevbcWyLBOcWWvdL YPv7ecnuSiy00N+7f+ChYRhSk6+HTph4f7mDMJbWkd6ugWorOzKjS6YqG0JAZHmStWk9 LcfhTIxE312OlgUaD+s8Rvw/FR0tfahl+821ZbxKeb7qg4IZqU93u76IUVMvn9sRUgy/ C7aBU3zL62yibHNI9wYEf0E3JQhpAIlj8kMyT9+IlFD31olty3dqCnVlvD1G4WzsbGzJ Ccgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=21RtI83U3AWt3cyeCJ2XmHc2ruDDyw09Go561vbFieg=; b=xlS5l7iPwsYyBfyJHn6aeV5yuUeyxvQRpPV9BgGp54oD0GMD7vY6kKYz/G/Ec6lDi5 5pDg0RctBpLeg/YvdAKiDmqKpqB6NC8E0b+AnK4ibSKBfcWu2jw8esx31gY6Oy6Y52aY 5DbJzPNdtMbUHwm18C2cFegMM4xWWsu5BxDBv+ZeJse2e1aXJwNmTguXhAxAjSdYQkne s0ER1DPNeePk7Q+Yre7mVWGpV3sLgOHI5wXbQyNwHd+fqouFipqnk7KcTszPIvLXEwhw rC6leJJQEs2Cn6lnWp8DCxgm1zQfTny8sgsCJR+aJwy0q8NxnkwuhJHTLzy3HNGVTKMv N7Bg== X-Gm-Message-State: ANoB5plcafSyCAjJiv8gaFjQuHJnqPVtKVn0IuheGreW3YhHzav9ipoA 1t+3sTzsP3G/DTrcnC+KRXG1e3ZWSeBf46MZ X-Google-Smtp-Source: AA0mqf44COThVTh8STo2F/PdfE1hAhOPrq1SYQrMQOFcuboOXsdNStHJxfmCn7TEZsRRJCXahEuHCw== X-Received: by 2002:a05:600c:3b04:b0:3cf:6fd8:95a4 with SMTP id m4-20020a05600c3b0400b003cf6fd895a4mr22693692wms.73.1669281560664; Thu, 24 Nov 2022 01:19:20 -0800 (PST) Received: from vermeer ([145.224.92.100]) by smtp.gmail.com with ESMTPSA id b10-20020adfde0a000000b0022e57e66824sm898859wrm.99.2022.11.24.01.19.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 24 Nov 2022 01:19:20 -0800 (PST) Date: Thu, 24 Nov 2022 10:19:16 +0100 From: Samuel Ortiz To: "Hongren (Zenithal) Zheng" Cc: Palmer Dabbelt , Paul Walmsley , Albert Ou , Atish Patra , Anup Patel , Eric Biederman , Kees Cook , linux-mm@kvack.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, linux-api@vger.kernel.org, Michael Kerrisk , linux-man@vger.kernel.org, Jiatai He , Heiko Stuebner , Conor.Dooley@microchip.com Subject: Re: [PATCH v3 1/3] RISC-V: add Bitmanip/Scalar Crypto parsing from DT Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ARC-Authentication-Results: i=1; imf06.hostedemail.com; dkim=pass header.d=rivosinc-com.20210112.gappssmtp.com header.s=20210112 header.b="7q/OaKPt"; spf=pass (imf06.hostedemail.com: domain of sameo@rivosinc.com designates 209.85.128.53 as permitted sender) smtp.mailfrom=sameo@rivosinc.com; dmarc=none ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1669281562; a=rsa-sha256; cv=none; b=OKtFF8854LZQHV3Wy89mnl1NBEomcTigeLK9EVHGbTxVBTQYp7MFVF6lB8g8svlMojoFvT 3K7dkusewh4MmIOc3oN+YZT9iOhzK4o39lAEd6LljD/RahFIHd83H7rMORDIYHZOUnB6cM Uxnc1zNAeIex5HkeMueFv4kSyj365Fk= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1669281562; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=21RtI83U3AWt3cyeCJ2XmHc2ruDDyw09Go561vbFieg=; b=sN77/3WXrwvoBF9zD7wRskjV+KKZWmcO9wwUa/BI7khLMRcuK+2zXE8kktBIs1YnL51u0m ev/bvQMYF7/i1vBWYxxfOk/xjDkGTUVq80AwF1xe1f3K/qDt3HjXilcNDAEHxcCE2bjg/S os9uzW787/z5yY479UlEfSKgqCu+21U= X-Rspam-User: Authentication-Results: imf06.hostedemail.com; dkim=pass header.d=rivosinc-com.20210112.gappssmtp.com header.s=20210112 header.b="7q/OaKPt"; spf=pass (imf06.hostedemail.com: domain of sameo@rivosinc.com designates 209.85.128.53 as permitted sender) smtp.mailfrom=sameo@rivosinc.com; dmarc=none X-Stat-Signature: aiaiaij9wopwbtd8yffjctf5shnwm4ca X-Rspamd-Queue-Id: 21623180007 X-Rspamd-Server: rspam09 X-HE-Tag: 1669281561-915394 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: Hi, On Mon, Jun 13, 2022 at 02:46:01AM +0800, Hongren (Zenithal) Zheng wrote: > This patch parses Zb/Zk related string from DT and > output them in cpuinfo > > One thing worth noting is that if DT provides zk, > all zbkb, zbkc, zbkx and zkn, zkr, zkt would be enabled. > > Note that zk is a valid extension name and the current > DT binding spec allows this. > > This patch also changes the logical id of > existing multi-letter extensions and adds a statement > that instead of logical id compatibility, the order > is needed. > > There currently lacks a mechanism to merge them when > producing cpuinfo. Namely if you provide a riscv,isa > "rv64imafdc_zk_zks", the cpuinfo output would be > "rv64imafdc_zbkb_zbkc_zbkx_zknd_zkne_zknh_zkr_zksed > _zksh_zkt" > > Tested-by: Jiatai He > Signed-off-by: Hongren (Zenithal) Zheng FWIW, after some rebasing: Tested-by: Samuel Ortiz Cheers, Samuel.