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 X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7C3A5C433E0 for ; Mon, 18 May 2020 12:29:56 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 4B25C20787 for ; Mon, 18 May 2020 12:29:56 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="JTkmw1Tp" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4B25C20787 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender: Content-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date: Message-ID:From:References:To:Subject:Reply-To:Content-ID:Content-Description :Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=utasvJJSV0z9xV5o1KsjRUdueW6yfttati3trG3zquc=; b=JTkmw1Tpr6qHAg 9UGFf+mAp8ABMcaVQAZ7bT4dyzKg2KHjb49hoBXE12w+TZQusntpCWwkFJFlp6mRY2DDztP5lc1tX PFotqNr0mPB9poclGfNXnZmQCBOisqgnDRvGVGKkS+LzvHV8rNxcuD7HUqmV9l/4847nbDpw/xz2O G9FpEb5gA0Xfa9C7oDlzGR7MHznXT5o2qUez11OhioQqFevd4x2SSVxXGJFMZWfekWb88Zs6xcW+z 4C4rfYUTmzL+HjEhjN6EMPjsGlYR5vR6jf+DVUPI/ubDywyLxPKKs1Id3Ws8uTI/ZPBwwbdX9OUjN dgv5W27sYGNpQ+oxs89w==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jaeu3-0005Tt-Aj; Mon, 18 May 2020 12:29:55 +0000 Received: from szxga06-in.huawei.com ([45.249.212.32] helo=huawei.com) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jaeu0-0005T3-EJ for linux-arm-kernel@lists.infradead.org; Mon, 18 May 2020 12:29:53 +0000 Received: from DGGEMS408-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id 3DD1DE0E47021E1364E8; Mon, 18 May 2020 20:29:49 +0800 (CST) Received: from [127.0.0.1] (10.173.220.25) by DGGEMS408-HUB.china.huawei.com (10.3.19.208) with Microsoft SMTP Server id 14.3.487.0; Mon, 18 May 2020 20:29:41 +0800 Subject: Re: [RFC PATCH v3 1/2] arm64: tlb: Detect the ARMv8.4 TLBI RANGE feature To: Anshuman Khandual , Mark Rutland References: <20200414112835.1121-1-yezhenyu2@huawei.com> <20200414112835.1121-2-yezhenyu2@huawei.com> <20200505101405.GB82424@C02TD0UTHF1T.local> <4d8cb48c-4f47-d966-f29b-3343bd966c5f@arm.com> From: Zhenyu Ye Message-ID: <9189159f-0df8-ef9a-5216-adc030856439@huawei.com> Date: Mon, 18 May 2020 20:29:39 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0 MIME-Version: 1.0 In-Reply-To: <4d8cb48c-4f47-d966-f29b-3343bd966c5f@arm.com> X-Originating-IP: [10.173.220.25] X-CFilter-Loop: Reflected X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200518_052952_642759_65AD0A3C X-CRM114-Status: UNSURE ( 8.85 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: linux-arch@vger.kernel.org, maz@kernel.org, suzuki.poulose@arm.com, catalin.marinas@arm.com, linux-kernel@vger.kernel.org, xiexiangyou@huawei.com, steven.price@arm.com, zhangshaokun@hisilicon.com, linux-mm@kvack.org, arm@kernel.org, prime.zeng@hisilicon.com, guohanjun@huawei.com, olof@lixom.net, kuhn.chenqun@huawei.com, will@kernel.org, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Anshuman, On 2020/5/18 12:22, Anshuman Khandual wrote: >>>> static const struct arm64_ftr_bits ftr_id_aa64isar0[] = { >>>> ARM64_FTR_BITS(FTR_VISIBLE, FTR_STRICT, FTR_LOWER_SAFE, ID_AA64ISAR0_RNDR_SHIFT, 4, 0), >>>> + ARM64_FTR_BITS(FTR_VISIBLE, FTR_STRICT, FTR_LOWER_SAFE, ID_AA64ISAR0_TLBI_RANGE_SHIFT, 4, 0), > > Hello Zhenyu, > > This is already being added through another patch [1] in a series [2] which primarily > has cpufeature changes. I will soon update the series making this feature FTR_HIDDEN. > > [1] https://patchwork.kernel.org/patch/11523881/ > [2] https://patchwork.kernel.org/project/linux-arm-kernel/list/?series=281211 > > I am planning to respin the series (V4) based on arm64 tree (for-next/cpufeature). So > could you please rebase this patch (probably dropping cpufeature related changes) on > upcoming V4, so that all the changes will be based on arm64 tree (for-next/cpufeature). > > - Anshuman > OK, I will rebase my patch based on your V4. Zhenyu _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel