[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9189159f-0df8-ef9a-5216-adc030856439@huawei.com>
Date: Mon, 18 May 2020 20:29:39 +0800
From: Zhenyu Ye <yezhenyu2@...wei.com>
To: Anshuman Khandual <anshuman.khandual@....com>,
Mark Rutland <mark.rutland@....com>
CC: <will@...nel.org>, <catalin.marinas@....com>,
<suzuki.poulose@....com>, <maz@...nel.org>, <steven.price@....com>,
<guohanjun@...wei.com>, <olof@...om.net>,
<linux-arch@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<xiexiangyou@...wei.com>, <zhangshaokun@...ilicon.com>,
<linux-mm@...ck.org>, <arm@...nel.org>, <prime.zeng@...ilicon.com>,
<kuhn.chenqun@...wei.com>, <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RFC PATCH v3 1/2] arm64: tlb: Detect the ARMv8.4 TLBI RANGE
feature
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
Powered by blists - more mailing lists