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.5 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,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 7A397C432C0 for ; Wed, 20 Nov 2019 08:47:55 +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 4F76E223D8 for ; Wed, 20 Nov 2019 08:47:55 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="aI3/t9Rn"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=kernel.org header.i=@kernel.org header.b="ttwn80sr" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 4F76E223D8 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org 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:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=dstGjxsES/AkrwOAHEOzY+e0iSUQuWbOWjTqVTB+rAg=; b=aI3/t9RnZ94xbK qlzPRhtNTdDPAQj7N/U/cBh2VXdmZTEMMqWs9X4WltYyPmyZkBnOis2DG5S6YoiuRkpPpbxcGfOUb tBY0OKO0RTGu/EgXb9amjbTErQTfBlUTJcLiqKC8BUjhW/ca4YIJJY44+uIyUHkS6ewnCBGBh0QD0 np8/iOLOn9GOT7ehLgTJ2Lwoa7P7eA1LewmUB3CPq3B/weRcJLHqYYiJ9S9x/kB6jPcfnO16ZKi9c Uv05WtDlPios8FW/g0EAOM+zhwv1OSDu9immyEonzgvKf9dGX3lAxe/OoF1MeOi4zwgy2ay8DdZyp QufXL0EiEcSKLc9PJ3dA==; 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 1iXLeU-0002k0-85; Wed, 20 Nov 2019 08:47:54 +0000 Received: from mail.kernel.org ([198.145.29.99]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1iXLeR-0002jc-Fb for linux-arm-kernel@lists.infradead.org; Wed, 20 Nov 2019 08:47:52 +0000 Received: from willie-the-truck (236.31.169.217.in-addr.arpa [217.169.31.236]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5348B2235D; Wed, 20 Nov 2019 08:47:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1574239670; bh=HT77a05SGzBXzjNW3SSpNiDG5j5REw2H7dE6GC1vlqw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ttwn80sr1LeO/JKisG3eqvjFBlcAPyy3jeFEd5ZKd5rahRFdeqK8H0MWc75ptXkd4 eGoAmSpbSK8i3/9CA52Wj/QgozmiPb3I0s/D8vS3t8HWxsAVgIi2E+bduTOZNwqYep IRUywIci9tg+K9eZ82tVjNNcVNlXOwgDCMz10lFI= Date: Wed, 20 Nov 2019 08:47:44 +0000 From: Will Deacon To: Marc Zyngier Subject: Re: [RFC PATCH v2] arm64: cpufeatures: add support for tlbi range instructions Message-ID: <20191120084743.GA20119@willie-the-truck> References: <5DC960EB.9050503@huawei.com> <20191111132716.GA9394@willie-the-truck> <5DC96660.8040505@huawei.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20191120_004751_547431_20AA292D X-CRM114-Status: GOOD ( 17.03 ) 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 , Zhenyu Ye , catalin.marinas@arm.com, suzuki.poulose@arm.com, linux-kernel@vger.kernel.org, xiexiangyou@huawei.com, Linuxarm , Shaokun Zhang , arm@kernel.org, tangnianyao@huawei.com, Hanjun Guo , 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 On Tue, Nov 19, 2019 at 10:03:34AM +0000, Marc Zyngier wrote: > On 2019-11-19 01:13, Hanjun Guo wrote: > > I'm thinking of how to add a firmware description for it, how about > > this: > > > > Adding a system level flag to indicate the supporting of TIBi by range, > > which means adding a binding name for example "tlbi-by-range" at system > > level in the dts file, or a tlbi by range flag in ACPI FADT table, then > > we use the ID register per-cpu and the system level flag as > > > > if (cpus_have_const_cap(ARM64_HAS_TLBI_BY_RANGE) && > > system_level_tlbi_by_range) > > flush_tlb_by_range() > > else > > flush_tlb_range() > > > > And this seems work for heterogeneous system (olny parts of the CPU > > support > > TLBi by range) as well, correct me if anything wrong. > > It could work, but it needs to come with the strongest guarantees that > all the DVM agents in the system understand this type of invalidation, > specially as we move into the SVM territory. It may also need to cope > with non-compliant agents being hot-plugged, or at least discovered late. > > 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). It would be good to get confirmation from Arm about this, since the TTL extension doesn't have the dangerous 'Note' that the range ops do and it wouldn't be difficult to ignore those bits in hardware where the system doesn't support the hint for all agents (in comparison to upgrading range ops to ALL, which may be unpalatable). Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel