From: David Hildenbrand <david@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: Ankit Agrawal <ankita@nvidia.com>,
"maz@kernel.org" <maz@kernel.org>,
"oliver.upton@linux.dev" <oliver.upton@linux.dev>,
"joey.gouly@arm.com" <joey.gouly@arm.com>,
"suzuki.poulose@arm.com" <suzuki.poulose@arm.com>,
"yuzenghui@huawei.com" <yuzenghui@huawei.com>,
"will@kernel.org" <will@kernel.org>,
"ryan.roberts@arm.com" <ryan.roberts@arm.com>,
"shahuang@redhat.com" <shahuang@redhat.com>,
"lpieralisi@kernel.org" <lpieralisi@kernel.org>,
Aniket Agashe <aniketa@nvidia.com>, Neo Jia <cjia@nvidia.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
"Tarun Gupta (SW-GPU)" <targupta@nvidia.com>,
Vikram Sethi <vsethi@nvidia.com>,
Andy Currid <acurrid@nvidia.com>,
Alistair Popple <apopple@nvidia.com>,
John Hubbard <jhubbard@nvidia.com>,
Dan Williams <danw@nvidia.com>, Zhi Wang <zhiw@nvidia.com>,
Matt Ochs <mochs@nvidia.com>, Uday Dhoke <udhoke@nvidia.com>,
Dheeraj Nigam <dnigam@nvidia.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"sebastianene@google.com" <sebastianene@google.com>,
"coltonlewis@google.com" <coltonlewis@google.com>,
"kevin.tian@intel.com" <kevin.tian@intel.com>,
"yi.l.liu@intel.com" <yi.l.liu@intel.com>,
"ardb@kernel.org" <ardb@kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"gshan@redhat.com" <gshan@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/1] KVM: arm64: Allow cacheable stage 2 mapping using VMA flags
Date: Fri, 17 Jan 2025 17:58:29 +0100 [thread overview]
Message-ID: <23fa05f8-ea30-4261-91d8-b34fc678c4de@redhat.com> (raw)
In-Reply-To: <20250117140050.GC5556@nvidia.com>
>> I don't see how VM_PFNMAP alone can tell us anything about the
>> access properties supported by a device address range. Either way,
>> it's the driver setting vm_page_prot or some VM_* flag. KVM has no
>> clue, it's just a memory slot.
>
> I think David's point about VM_PFNMAP was to avoid some of the
> pfn_valid() logic. If we get VM_PFNMAP we just assume it is non-struct
> page and follow the VMA's pgprot.
Exactly what I meant.
If we only expect DEVICE stuff in VM_PFNMAP, then we can limit all the
weirdness (and figuring out what todo using pgprot etc) to exactly that.
VM_IO without VM_PFNMAP might be interesting; not sure if we even want
to support that here.
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-01-17 16:58 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 [this message]
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
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=23fa05f8-ea30-4261-91d8-b34fc678c4de@redhat.com \
--to=david@redhat.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=jgg@nvidia.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
Powered by JetHome