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=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 9215DC2BB1D for ; Tue, 17 Mar 2020 11:00:04 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 5D6442071C for ; Tue, 17 Mar 2020 11:00:04 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5D6442071C Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 0CEA06B0005; Tue, 17 Mar 2020 07:00:04 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 0807C6B0007; Tue, 17 Mar 2020 07:00:04 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id EFE846B0008; Tue, 17 Mar 2020 07:00:03 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0228.hostedemail.com [216.40.44.228]) by kanga.kvack.org (Postfix) with ESMTP id D619F6B0005 for ; Tue, 17 Mar 2020 07:00:03 -0400 (EDT) Received: from smtpin29.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id 9756D5825 for ; Tue, 17 Mar 2020 11:00:03 +0000 (UTC) X-FDA: 76604559486.29.corn00_746ddbf54f00c X-HE-Tag: corn00_746ddbf54f00c X-Filterd-Recvd-Size: 3018 Received: from huawei.com (szxga05-in.huawei.com [45.249.212.191]) by imf14.hostedemail.com (Postfix) with ESMTP for ; Tue, 17 Mar 2020 10:59:59 +0000 (UTC) Received: from DGGEMS401-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id CC8CE9A663F0575FBBF9; Tue, 17 Mar 2020 18:59:51 +0800 (CST) Received: from [127.0.0.1] (10.173.220.25) by DGGEMS401-HUB.china.huawei.com (10.3.19.201) with Microsoft SMTP Server id 14.3.487.0; Tue, 17 Mar 2020 18:59:42 +0800 Subject: Re: [RFC PATCH v1 0/3] arm64: tlb: add support for TTL field To: Marc Zyngier CC: , , , , , , , , , , , , , , References: <20200311025309.1743-1-yezhenyu2@huawei.com> <247ad619edf17eb266f856d937dac826@kernel.org> From: "yezhenyu (A)" Message-ID: Date: Tue, 17 Mar 2020 18:59:40 +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: <247ad619edf17eb266f856d937dac826@kernel.org> Content-Type: text/plain; charset="UTF-8" X-Originating-IP: [10.173.220.25] X-CFilter-Loop: Reflected Content-Transfer-Encoding: quoted-printable 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 Marc, On 2020/3/11 17:12, Marc Zyngier wrote: > Zhenyu, >=20 > On 2020-03-11 02:53, Zhenyu Ye wrote: >> ARMv8.4-TTL provides the TTL field in tlbi instruction to indicate >> the level of translation table walk holding the leaf entry for the >> address that is being invalidated. Hardware can use this information >> to determine if there was a risk of splintering. >> >> This set of patches adds TTL field to __TLBI_ADDR, and uses >> Architecture-specific MM context to pass the TTL value to tlb interfac= e. >> >> The default value of TTL is 0, which will not have any impact on the >> TLB maintenance instructions. The last patch trys to use TTL field in >> some obviously tlb-flush interface. >=20 > I have already posted some support for ARMv8.4-TTL as part of my NV ser= ies [1], > patches 62, 67, 68 and 69. This only deals with Stage-2 translation so = far. > If you intend to add Stage-1, please build on top of what I have alread= y posted > (I can extract the patches on a separate branch if you want). >=20 > Thanks, >=20 > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 M. >=20 > [1] https://lore.kernel.org/linux-arm-kernel/20200211174938.27809-1-maz= @kernel.org/ I have sent the PATCH v2 on 2020-03-12 [1]. Do you have any suggestion for my code? Is it appropriate to post my code based on your branch? Looking forward to your suggestions. Thanks, zhenyu [1] https://lkml.org/lkml/2020/3/12/2 =09