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.2 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,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 4151CC2BB85 for ; Fri, 10 Apr 2020 01:44:20 +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 0E65A2074F for ; Fri, 10 Apr 2020 01:44:19 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="gz3tD107" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0E65A2074F 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-Type: Content-Transfer-Encoding:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:Date:Message-ID:References: To:From:Subject:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=Z01IsTm4fy5BSwEE/gX7ZUsYMdVXdTj51GO9RHlWbc4=; b=gz3tD107FQ+bwofUfGuYm1Xxp RpVP1V93EZR2ViP/XGNUNUztx+YpToDPfbtpTacJeg9gTL4ipCg8eeLpcgcizb1lXOTUOSKIJ4QJ9 GJRrtcn9cPMz+SgrjcpBnXH9AGR9jpb2pqv4P+yE4wx1eWlZWw62+iKE017u4hKbh34Oy/+G0iAkf l/IOJCz/cyX2DLkIDlzjRdF3BSWrqw2oaUo0Z0dn3KRZXMhH7NUQguu4WpeZLVnOdvYPp69krZqd3 paNrxyUO2mvudje2J7/CG2cwByg4torWajfEIr8uGW9TgmzF3dM1mMl27RbqS1LzXjMi48vgpx/Sp 9oh6PHr9Q==; 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 1jMiiQ-0001OP-AU; Fri, 10 Apr 2020 01:44:18 +0000 Received: from szxga04-in.huawei.com ([45.249.212.190] helo=huawei.com) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jMiiK-0001GA-PV for linux-arm-kernel@lists.infradead.org; Fri, 10 Apr 2020 01:44:15 +0000 Received: from DGGEMS406-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 6B2A413EDA8019B845EB; Fri, 10 Apr 2020 09:43:56 +0800 (CST) Received: from [127.0.0.1] (10.173.220.190) by DGGEMS406-HUB.china.huawei.com (10.3.19.206) with Microsoft SMTP Server id 14.3.487.0; Fri, 10 Apr 2020 09:43:50 +0800 Subject: Re: [RFC PATCH v2] arm64: cpufeatures: add support for tlbi range instructions From: Hanjun Guo To: , Rob Herring , , 'Matteo Carlini' References: <5DC960EB.9050503@huawei.com> <20191111132716.GA9394@willie-the-truck> <5DC96660.8040505@huawei.com> <3b833c82-2c1b-462a-f06f-d4c8b373dac1@huawei.com> Message-ID: Date: Fri, 10 Apr 2020 09:43:49 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <3b833c82-2c1b-462a-f06f-d4c8b373dac1@huawei.com> Content-Language: en-GB X-Originating-IP: [10.173.220.190] X-CFilter-Loop: Reflected X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200409_184413_813974_7B83704E X-CRM114-Status: GOOD ( 12.12 ) 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: mark.rutland@arm.com, wanghuiqiang , suzuki.poulose@arm.com, Marc Zyngier , Zhenyu Ye , Linuxarm , xiexiangyou@huawei.com, Shaokun Zhang , tangnianyao@huawei.com, Will Deacon , linux-arm-kernel@lists.infradead.org, qiuzhenfa@hisilicon.com Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi ARM folks, On 2019/11/20 9:29, Hanjun Guo wrote: >> >> I also wonder if the ARMv8.4-TTL extension (which I have patches for in >> the nested virt series) requires the same kind of treatment (after all, >> it has an implicit range based on the base granule size and level). >> >> In any way, this requires careful specification, and I don't think >> we can improvise this on the ML... ;-) > > Sure :), the good news is that ARM officially announced will be > working with Huawei again. > > So if I understand your point correctly, we need steps to take: > - ARM spec needs to make TIBi by range crystal clear and being > written down in the spec; > - Firmware description of supporting TLBi by range in system level > for both FDT and ACPI; > - Then upstream the code. Do we have update here? I noticed that the TLBI by rang for SMMU is merged for upstream from Rob, any plan or progress for the CPU side? Sorry to ping you on the mailling list, our upcoming new chip has this feature and it's good to enable it, so it's a bit urgent for us. Best regards, Hanjun _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel