Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp3901769ybe; Mon, 9 Sep 2019 00:34:31 -0700 (PDT) X-Google-Smtp-Source: APXvYqzWg9Wz8T6nEp+z92TCbkVp/SdeoMnMlj9WW8kTI6fuupgEOF4UaPZTrH4ymDc47mgiTYJG X-Received: by 2002:a05:6402:17ae:: with SMTP id j14mr22604243edy.219.1568014470906; Mon, 09 Sep 2019 00:34:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568014470; cv=none; d=google.com; s=arc-20160816; b=AqdkO4B1S4e09VrJ67EIrh1C3dCmY1RiXYoUO5qbJqrakd626d2Lz4CFDq7go861ZX /TGUSsPl5hupZyoAW8s1zdRehwmVB+WdRyWqkJ4/HbiMEa3gnagiRNNhiEmyBBUFUdYI sm4HwvOZRgCbx/pbr5jCfhAemXx93aA+JwCOT4LiwuNkgmSmkPY1MFTt25vMhppDslxi kKK6N7c6ndQpe1/aH3L3jcUaARQmZfLPbyZZJC/rSgFBCOQpWl2H0IzIxGkwscLnsB1O 8ODIGd8a5/nwxEDOHmFUr7j62wO7WI7d5+GWOdVF0RTN5YustvhgwTv6dei//NsgjM9x tIcg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=KU+yu1dnpjqMkvaxD0NQ/62kFYi8GAP69zuvLWhpBPg=; b=lImT7xF4UObsBn6Ul05SOTfwpgUedNNShwERcHyVs7A/cOzQRQy86yYzTgYEO4Zn/F xKWy9VJqyCTbOwXEbzESktvBMVRVw/ivYcGexGx2NMkiBAEm76aFWqYPK3DZvVuU+TTC ff9hu35lQii2Ojy24tFMC4JfRcpFdC2fqgUTnczh4VHYUsuvjdhPaDncgnV7ht6vtM50 ASSaAJJ69e6/EyMhZabg9KiuN54klgDUa8pGo1thzdv34y+iu5mQ4bqHBcPNU7VNF5vJ /4Lq0PaZfSCghc7OdsrDAcbA3pS1lbyNCZeFsuATLpckW3YoAMZ2NlLazxnIWwL68zGy l3Ig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=iQhzSJ+9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n13si7684238edq.98.2019.09.09.00.34.07; Mon, 09 Sep 2019 00:34:30 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=iQhzSJ+9; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731259AbfIGXxJ (ORCPT + 99 others); Sat, 7 Sep 2019 19:53:09 -0400 Received: from mail.kernel.org ([198.145.29.99]:46882 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726881AbfIGXxJ (ORCPT ); Sat, 7 Sep 2019 19:53:09 -0400 Received: from mail-wm1-f53.google.com (mail-wm1-f53.google.com [209.85.128.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 5F734206C3 for ; Sat, 7 Sep 2019 23:53:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1567900388; bh=KU+yu1dnpjqMkvaxD0NQ/62kFYi8GAP69zuvLWhpBPg=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=iQhzSJ+9oXgDhIW7PRJgS7OAd27+ApcmlwV1Pr1t7tIdVxFSSbNmEPtHB+EVkx/QI 3oFy7UEQ8OJz3CxRjUYWmyWOwvSBH4uR+n5qkd1ZBcZeaqG5m2rMeo15JOhhtEIi6O gZUNlX9yNbmazWAWH7DCrTZAkCxjkeJuFftVnO9s= Received: by mail-wm1-f53.google.com with SMTP id t9so10749522wmi.5 for ; Sat, 07 Sep 2019 16:53:08 -0700 (PDT) X-Gm-Message-State: APjAAAV5zr6sGHvFNRXfr6UM5bVWv0h+XxAI0+rRIsXa3iWgMSPEiijn hCdCaQ6lfgIrJj+mkJLSb9kvudS7Z7UjmODUoWY= X-Received: by 2002:a1c:f007:: with SMTP id a7mr12784687wmb.172.1567900386906; Sat, 07 Sep 2019 16:53:06 -0700 (PDT) MIME-Version: 1.0 References: <20190321163623.20219-1-julien.grall@arm.com> <20190321163623.20219-12-julien.grall@arm.com> <0dfe120b-066a-2ac8-13bc-3f5a29e2caa3@arm.com> <20190619091219.GB7767@fuggles.cambridge.arm.com> <20190619123939.GF7767@fuggles.cambridge.arm.com> <20190624104006.lvm32nahemaqklxc@willie-the-truck> In-Reply-To: <20190624104006.lvm32nahemaqklxc@willie-the-truck> From: Guo Ren Date: Sun, 8 Sep 2019 07:52:55 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH RFC 11/14] arm64: Move the ASID allocator code in a separate file To: Will Deacon Cc: Will Deacon , julien.thierry@arm.com, aou@eecs.berkeley.edu, james.morse@arm.com, Arnd Bergmann , suzuki.poulose@arm.com, Marc Zyngier , Catalin Marinas , Anup Patel , Linux Kernel Mailing List , Mike Rapoport , Christoph Hellwig , Atish Patra , Julien Grall , Palmer Dabbelt , gary@garyguo.net, Paul Walmsley , christoffer.dall@arm.com, linux-riscv@lists.infradead.org, kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org, iommu@lists.linux-foundation.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Thx Will, On Mon, Jun 24, 2019 at 6:40 PM Will Deacon wrote: > > I'll keep my system use the same ASID for SMP + IOMMU :P > > You will want a separate allocator for that: > > https://lkml.kernel.org/r/20190610184714.6786-2-jean-philippe.brucker@arm.com Yes, it is hard to maintain ASID between IOMMU and CPUMMU or different system, because it's difficult to synchronize the IO_ASID when the CPU ASID is rollover. But we could still use hardware broadcast TLB invalidation instruction to uniformly manage the ASID and IO_ASID, or OTHER_ASID in our IOMMU. Welcome to join our disscusion: "Introduce an implementation of IOMMU in linux-riscv" 9 Sep 2019, 10:45 Jade-room-I&II (Corinthia Hotel Lisbon) RISC-V MC -- Best Regards Guo Ren ML: https://lore.kernel.org/linux-csky/