From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 113E6675DB; Tue, 5 Dec 2023 18:40:49 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6FAB3C433C7; Tue, 5 Dec 2023 18:40:45 +0000 (UTC) Date: Tue, 5 Dec 2023 18:40:42 +0000 From: Catalin Marinas To: Marc Zyngier Cc: Jason Gunthorpe , ankita@nvidia.com, Shameerali Kolothum Thodi , oliver.upton@linux.dev, suzuki.poulose@arm.com, yuzenghui@huawei.com, will@kernel.org, ardb@kernel.org, akpm@linux-foundation.org, gshan@redhat.com, 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, mochs@nvidia.com, kvmarm@lists.linux.dev, kvm@vger.kernel.org, lpieralisi@kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 1/1] KVM: arm64: allow the VM to select DEVICE_* and NORMAL_NC for IO memory Message-ID: References: <20231205033015.10044-1-ankita@nvidia.com> <86fs0hatt3.wl-maz@kernel.org> <20231205130517.GD2692119@nvidia.com> <20231205164318.GG2692119@nvidia.com> <86bkb4bn2v.wl-maz@kernel.org> <86a5qobkt8.wl-maz@kernel.org> Precedence: bulk X-Mailing-List: kvm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86a5qobkt8.wl-maz@kernel.org> On Tue, Dec 05, 2023 at 05:50:27PM +0000, Marc Zyngier wrote: > On Tue, 05 Dec 2023 17:33:01 +0000, > Catalin Marinas wrote: > > Ideally we should do this for vfio only but we don't have an easy > > way to convey this to KVM. > > But if we want to limit this to PCIe, we'll have to find out. The > initial proposal (a long while ago) had a flag conveying some > information, and I'd definitely feel more confident having something > like that. We can add a VM_PCI_IO in the high vma flags to be set by vfio_pci_core_mmap(), though it limits it to 64-bit architectures. KVM knows this is PCI and relaxes things a bit. It's not generic though if we need this later for something else. A question for Lorenzo: do these BARs appear in iomem_resource? We could search that up instead of a flag, something like the page_is_ram() helper. -- Catalin