Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp523657pxb; Wed, 27 Jan 2021 13:51:27 -0800 (PST) X-Google-Smtp-Source: ABdhPJwAo8IIlzrW7M6qwmuSU5ei2POtrsPL0+AAUAM9T7bPK1xUZ+0N2HRCcTULc8LXNreJ+Kb4 X-Received: by 2002:a05:6402:1c0f:: with SMTP id ck15mr10555160edb.171.1611784286969; Wed, 27 Jan 2021 13:51:26 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611784286; cv=none; d=google.com; s=arc-20160816; b=Ul4DDjnqi/JFsX8N0zqZ90mclK7mb/z3Wif0IFve+zMZlzoX2q4IdP1pfdUgN75uxb dNXF2vYzQttQpx/sKfPkM8uCPg6jbmcjOAu6UO/MFKeMEJNL1rYrsCB+pYdEsi3vrh85 1VrSsSIkt0pocxxyOEpuqOX4r5YOMsxPtZreMzFgmxmwT+kvfGzA1hvhVyk6cd2JyiFY +9VLraclCa+XlH2XRB62K6GBexv0ByZ17Qb+2ncJmg2E8oSqMMs2cbA2PHXwidKFSHAf IQR0T/meDwNA3b8ycLlxot5B0KvCpZRTVWigjcgdoBUosfp2AfEsZI/6rKfsvkA4AoMg 1nJg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=RspId7Jee0hX1nfQIiyuXltth2gefs7sF/OIsTd6mTY=; b=mjlw3UFN7TApdj34J8C7bZxJy6T8rxAOFJtmTle5teeCeIo3LWRFvRDEsn6HB+j9XX D5tRj7ecsRUsoxZpvNNHoWneuwrb2bUE5KkBeXLhiIFxVlHp2nO2DMaFY6TYMi5CHz+k pxOxnJWjNWKesMGR1T60ffMAHDOCB/k2NCX6XOD9tnn72XAaz1NKOY7AhrtJyYkkfMd8 f9KzlMSRHjQFW8E5Gzb3HqXxqASrABBC0DIZ8dQ9RD+W/1MjF5oXufk4WlMvw5fTlzjo wl8epTN1UkL/Tx5kfqgWZT+1vYyttC/KQoVg3UiPv8A2UGBIkU/zVPCzqQqe+TBh0CUI +Rjg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id hr20si1411681ejc.23.2021.01.27.13.51.01; Wed, 27 Jan 2021 13:51:26 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234721AbhA0Jmu (ORCPT + 99 others); Wed, 27 Jan 2021 04:42:50 -0500 Received: from foss.arm.com ([217.140.110.172]:35176 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233844AbhA0Jk0 (ORCPT ); Wed, 27 Jan 2021 04:40:26 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 8957131B; Wed, 27 Jan 2021 01:39:40 -0800 (PST) Received: from [10.57.46.236] (unknown [10.57.46.236]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 65DC03F66B; Wed, 27 Jan 2021 01:39:39 -0800 (PST) Subject: Re: [PATCH 1/1] iommu/arm-smmu-v3: add support for BBML To: Keqian Zhu , Will Deacon Cc: Jean-Philippe Brucker , linux-kernel , iommu , Yang Yingliang , linux-arm-kernel References: <20201126034230.777-1-thunder.leizhen@huawei.com> <20210122125132.GB24102@willie-the-truck> <1bfd1ca0-953e-e943-f87e-144d5537bd0c@arm.com> <20210126101230.GA29204@willie-the-truck> <8a9685ec-67aa-824f-5429-f408bf79c5ab@huawei.com> <32f4752f-6954-183a-a0c1-b5d719c85b67@huawei.com> From: Robin Murphy Message-ID: <319e3532-4555-7431-9d6f-3c3b7c11a5d9@arm.com> Date: Wed, 27 Jan 2021 09:39:38 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; rv:78.0) Gecko/20100101 Thunderbird/78.6.1 MIME-Version: 1.0 In-Reply-To: <32f4752f-6954-183a-a0c1-b5d719c85b67@huawei.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021-01-27 07:36, Keqian Zhu wrote: > > > On 2021/1/27 10:01, Leizhen (ThunderTown) wrote: >> >> >> On 2021/1/26 18:12, Will Deacon wrote: >>> On Mon, Jan 25, 2021 at 08:23:40PM +0000, Robin Murphy wrote: >>>> Now we probably will need some degreee of BBML feature awareness for the >>>> sake of SVA if and when we start using it for CPU pagetables, but I still >>>> cannot see any need to consider it in io-pgtable. >>> >>> Agreed; I don't think this is something that io-pgtable should have to care >>> about. > Hi, > > I have a question here :-). > If the old table is not live, then the break procedure seems unnecessary. Do I miss something? The MMU is allowed to prefetch translations at any time, so not following the proper update procedure could still potentially lead to a TLB conflict, even if there's no device traffic to worry about disrupting. Robin. > Thanks, > Keqian > >> >> Yes, the SVA works in stall mode, and the failed device access requests are not >> discarded. >> >> Let me look for examples. The BBML usage scenario was told by a former colleague. >> >>> >>> Will >>> >>> . >>> >> >> >> _______________________________________________ >> linux-arm-kernel mailing list >> linux-arm-kernel@lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >> . >> > _______________________________________________ > iommu mailing list > iommu@lists.linux-foundation.org > https://lists.linuxfoundation.org/mailman/listinfo/iommu >