Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp405135ybn; Tue, 1 Oct 2019 23:29:28 -0700 (PDT) X-Google-Smtp-Source: APXvYqwHYE7Cyi8MWzJvveXofNyRVSgNChXOjm+UBaxKKkVMnKvexfsCfQGJZ6IKr5kxaIJ1NuqX X-Received: by 2002:a05:6402:121a:: with SMTP id c26mr2145631edw.100.1569997768477; Tue, 01 Oct 2019 23:29:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569997768; cv=none; d=google.com; s=arc-20160816; b=0/u/L3jsniqf8uDhw5KxyIeSKeMm4IgBM3PaUFdBbOkaKjrSQ4M1F4NIrVu7Mg7E0u GZzOKWDjPScoxJV7Y9a7/I9oLNxu4fA3SexE1VixJFA9D4fSCGG1n2Cr4B07sql123HQ HI3G+2nKshGvyYqmSc3K0RQ7nYivfWh7KLly3KpVWHRQhLt1OjblXLwEUEaNe3vYN7Pn wAEA/vsrDNlKN5+KyVJaPz+zI+CW+9dJSo7s2XF5drl1rDVdwz/CiwAF+z+m1Yxu8q6p Ogc7QlR99o1FLp/sYgE+FmLInG+uwL8pk28KvB94mdayEEVRQLdwO3lcVV5DE+eRruw2 WCbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=Rf1F02DF+ApX70kLZfw1Tx7xtR4gl35KTJrV99TDdBg=; b=TFEWq8I/0VufJUF8lmYP4lTe5OEPKTuciNyiim6zkwJI8clsnsYv8hEPVX/+0/W86Q tmRp+lr2txYckKL7AhL9NRe4OYLA+nDCBdqrE2mut137oIgVPxtuvbXCTAlowAc/fu+p RrvbSkCXLyAVDc6BhMA606kxcSE10b7u+0BZtQjfArvVsIT0JY9cXOWqxtpN6Q7hAtNB CEDWDCepPgLcTxMUkWM5hvmgEctaNqI88fm+TyRSbsW+z3y1vd12FBXc/7penb4YDgEs W2ZUoEE+tgBmqoNNoZFMB728UwHh1OsIZIbCWc5oTXUbg3oSoAirD0Dns1oA3vIjJpCG uumQ== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id qo6si10297021ejb.386.2019.10.01.23.29.04; Tue, 01 Oct 2019 23:29:28 -0700 (PDT) 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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727165AbfJBByR (ORCPT + 99 others); Tue, 1 Oct 2019 21:54:17 -0400 Received: from 59-120-53-16.HINET-IP.hinet.net ([59.120.53.16]:16231 "EHLO ATCSQR.andestech.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726067AbfJBByR (ORCPT ); Tue, 1 Oct 2019 21:54:17 -0400 Received: from mail.andestech.com (atcpcs16.andestech.com [10.0.1.222]) by ATCSQR.andestech.com with ESMTP id x921cDgV024925; Wed, 2 Oct 2019 09:38:13 +0800 (GMT-8) (envelope-from alankao@andestech.com) Received: from andestech.com (10.0.15.65) by ATCPCS16.andestech.com (10.0.1.222) with Microsoft SMTP Server id 14.3.123.3; Wed, 2 Oct 2019 09:53:39 +0800 Date: Wed, 2 Oct 2019 09:53:39 +0800 From: Alan Kao To: "hch@infradead.org" CC: Atish Patra , "aou@eecs.berkeley.edu" , "anup@brainfault.org" , "palmer@sifive.com" , "linux-kernel@vger.kernel.org" , "johan@kernel.org" , "paul.walmsley@sifive.com" , "linux-riscv@lists.infradead.org" Subject: Re: [v6 PATCH] RISC-V: Remove unsupported isa string info print Message-ID: <20191002015338.GA28086@andestech.com> References: <20191001002318.7515-1-atish.patra@wdc.com> <20191001070236.GA7622@infradead.org> <20191001101016.GB23507@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20191001101016.GB23507@infradead.org> User-Agent: Mutt/1.5.24 (2015-08-30) X-Originating-IP: [10.0.15.65] X-DNSRBL: X-MAIL: ATCSQR.andestech.com x921cDgV024925 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 01, 2019 at 03:10:16AM -0700, hch@infradead.org wrote: > On Tue, Oct 01, 2019 at 08:22:37AM +0000, Atish Patra wrote: > > riscv_of_processor_hartid() or seems to be a better candidate. We > > already check if "rv" is present in isa string or not. I will extend > > that to check for rv64i or rv32i. Is that okay ? > > I'd rather lift the checks out of that into a function that is called > exactly once per hart on boot (and future cpu hotplug). Sorry that I am a bit out of date on this. Is there any related discussion about such checks? Just want to make sure if the check stops here and will not go any further for extensions, Xs and Zs. > > _______________________________________________ > linux-riscv mailing list > linux-riscv@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-riscv