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
Date: Mon, 4 Apr 2022 10:24:05 -0300 [thread overview]
Message-ID: <20220404132405.GQ64706@ziepe.ca> (raw)
In-Reply-To: <87tubcbvgk.wl-maz@kernel.org>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-04 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 9:08 [PATCH v2] kvm/arm64: fixed passthrough gpu into vm on arm64 xieming
2022-04-01 14:19 ` Jason Gunthorpe
2022-04-01 16:48 ` Marc Zyngier
2022-04-04 13:24 ` Jason Gunthorpe [this message]
2022-04-04 14:47 ` Marc Zyngier
2022-04-04 17:02 ` Jason Gunthorpe
2022-04-05 15:27 ` Marc Zyngier
2022-04-05 16:51 ` Jason Gunthorpe
2022-04-06 8:17 ` Tian, Kevin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220404132405.GQ64706@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=alex.williamson@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maz@kernel.org \
--cc=sashal@kernel.org \
--cc=will@kernel.org \
--cc=xieming@kylinos.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).