From: Jason Gunthorpe <jgg@nvidia.com>
To: Will Deacon <will@kernel.org>
Cc: ankita@nvidia.com, maz@kernel.org, oliver.upton@linux.dev,
joey.gouly@arm.com, suzuki.poulose@arm.com, yuzenghui@huawei.com,
catalin.marinas@arm.com, ryan.roberts@arm.com,
shahuang@redhat.com, lpieralisi@kernel.org, aniketa@nvidia.com,
cjia@nvidia.com, kwankhede@nvidia.com, targupta@nvidia.com,
vsethi@nvidia.com, acurrid@nvidia.com, apopple@nvidia.com,
jhubbard@nvidia.com, danw@nvidia.com, zhiw@nvidia.com,
mochs@nvidia.com, udhoke@nvidia.com, dnigam@nvidia.com,
alex.williamson@redhat.com, sebastianene@google.com,
coltonlewis@google.com, kevin.tian@intel.com, yi.l.liu@intel.com,
ardb@kernel.org, akpm@linux-foundation.org, gshan@redhat.com,
linux-mm@kvack.org, kvmarm@lists.linux.dev, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 0/1] KVM: arm64: Map GPU memory with no struct pages
Date: Tue, 10 Dec 2024 10:18:06 -0400 [thread overview]
Message-ID: <20241210141806.GI2347147@nvidia.com> (raw)
In-Reply-To: <20241210140739.GC15607@willie-the-truck>
On Tue, Dec 10, 2024 at 02:07:40PM +0000, Will Deacon wrote:
> On Mon, Nov 18, 2024 at 01:19:57PM +0000, ankita@nvidia.com wrote:
> > The changes are heavily influenced by the insightful discussions between
> > Catalin Marinas and Jason Gunthorpe [1] on v1. Many thanks for their
> > valuable suggestions.
> >
> > Link: https://lore.kernel.org/lkml/20230907181459.18145-2-ankita@nvidia.com [1]
>
> That's a different series, no? It got merged at v9:
I was confused by this too. v1 of that series included this patch, as
that series went along it became focused only on enabling WC
(Normal-NC) in a VM for device MMIO and this patch for device cachable
memory was dropped off.
There are two related things:
1) Device MMIO memory should be able to be Normal-NC in a VM. Already
merged
2) Device Cachable memory (ie CXL and pre-CXL coherently attached
memory) should be Normal Cachable in a VM, even if it doesn't have
struct page/etc. (this patch)
IIRC this part was dropped off because of the MTE complexity that
Catalin raised.
Jason
next prev parent reply other threads:[~2024-12-10 14:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 13:19 [PATCH v2 0/1] KVM: arm64: Map GPU memory with no struct pages ankita
2024-11-18 13:19 ` [PATCH v2 1/1] KVM: arm64: Allow cacheable stage 2 mapping using VMA flags ankita
2024-12-10 14:13 ` Will Deacon
2024-12-11 2:58 ` Ankit Agrawal
2024-12-11 21:49 ` Will Deacon
2024-12-11 22:01 ` Catalin Marinas
2025-01-10 21:04 ` Ankit Agrawal
2024-12-20 15:42 ` David Hildenbrand
2025-01-06 16:51 ` Jason Gunthorpe
2025-01-08 16:09 ` David Hildenbrand
2025-01-10 21:15 ` Ankit Agrawal
2025-01-13 16:27 ` Jason Gunthorpe
2025-01-14 13:17 ` David Hildenbrand
2025-01-14 13:31 ` Jason Gunthorpe
2025-01-14 23:13 ` Ankit Agrawal
2025-01-15 14:32 ` Jason Gunthorpe
2025-01-16 22:28 ` Catalin Marinas
2025-01-17 14:00 ` Jason Gunthorpe
2025-01-17 16:58 ` David Hildenbrand
2025-01-17 17:10 ` Jason Gunthorpe
2025-01-17 18:52 ` Catalin Marinas
2025-01-17 19:16 ` Jason Gunthorpe
2024-11-26 17:10 ` [PATCH v2 0/1] KVM: arm64: Map GPU memory with no struct pages Donald Dutile
2024-12-02 4:51 ` Ankit Agrawal
2024-12-10 14:07 ` Will Deacon
2024-12-10 14:18 ` Jason Gunthorpe [this message]
2024-12-10 14:45 ` Catalin Marinas
2024-12-10 15:56 ` Donald Dutile
2024-12-10 16:08 ` Catalin Marinas
2024-12-11 3:05 ` Ankit Agrawal
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=20241210141806.GI2347147@nvidia.com \
--to=jgg@nvidia.com \
--cc=acurrid@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=aniketa@nvidia.com \
--cc=ankita@nvidia.com \
--cc=apopple@nvidia.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cjia@nvidia.com \
--cc=coltonlewis@google.com \
--cc=danw@nvidia.com \
--cc=dnigam@nvidia.com \
--cc=gshan@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=joey.gouly@arm.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=kwankhede@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lpieralisi@kernel.org \
--cc=maz@kernel.org \
--cc=mochs@nvidia.com \
--cc=oliver.upton@linux.dev \
--cc=ryan.roberts@arm.com \
--cc=sebastianene@google.com \
--cc=shahuang@redhat.com \
--cc=suzuki.poulose@arm.com \
--cc=targupta@nvidia.com \
--cc=udhoke@nvidia.com \
--cc=vsethi@nvidia.com \
--cc=will@kernel.org \
--cc=yi.l.liu@intel.com \
--cc=yuzenghui@huawei.com \
--cc=zhiw@nvidia.com \
/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).