Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Mon, 4 Apr 2022 10:24:05 -0300
From:   Jason Gunthorpe <jgg@ziepe.ca>
To:     Marc Zyngier <maz@kernel.org>
Cc:     xieming <xieming@kylinos.cn>, sashal@kernel.org,
        catalin.marinas@arm.com, linux@armlinux.org.uk,
        linux-kernel@vger.kernel.org, alex.williamson@redhat.com,
        will@kernel.org, kvmarm@lists.cs.columbia.edu,
        linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] kvm/arm64: fixed passthrough gpu into vm on arm64
Message-ID: <20220404132405.GQ64706@ziepe.ca>
References: <20220401090828.614167-1-xieming@kylinos.cn>
 <87tubcbvgk.wl-maz@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87tubcbvgk.wl-maz@kernel.org>
Precedence: bulk

On Fri, Apr 01, 2022 at 05:48:59PM +0100, Marc Zyngier wrote:

> NAK. For a start, there is no such thing as 'write-combine' in the ARM
> architecture, and I'm not convinced you can equate WC to Normal-NC.
> See the previous discussion at [1].
> 
> [1] https://lore.kernel.org/r/20210429162906.32742-1-sdonthineni@nvidia.com

We've had a lot of discussions with ARM related to how this works with
drivers like mlx5 that use WC.

ARM has now published some guidance on this:

https://community.arm.com/arm-research/m/resources/1012

As an ecosystem we seem to be drifting toward Normal-NC for this
behavior (largely because it is what Linux does). At least that is
what we are testing and qualifing ARM CPUs against mlx5 with.

I'm guessing it will turn into a SBSA like thing where the ARM ARM is
kind of vauge but a SOC has to implement Normal-NC in a certain way to
be functional for the server market.

Jason