From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wm1-f46.google.com (mail-wm1-f46.google.com [209.85.128.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 123D1473C6D for ; Fri, 16 Oct 2026 10:57:58 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.128.46 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1792148288; cv=none; b=FCbO+lcmQCe4uPJYdOAz7yDnvmhU0yb0zkqLJkn6URaKD4GzfCrEacH/oHUHqNyh6Afu1nJBuv5igg+FYMAJfw/epxFUhr/Hwc0aOj8VY7S3TPYAXddgzp2RVSO7TSVHbDSTSK3xyQGHj8nrwA8UQdvm+gRcekLZliZeDiSOV4I= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1792148288; c=relaxed/simple; bh=Fg04sF4wbeMFqUdM8zmoRfU3uiwkIyCVmr/Efwdeo90=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=nodXIjlkWrz57rmlZC8JgY17HkJeqKhbzKWL7rMvyMvyH6JU2rlDGfegbaicfkTGAjKLTiJreyjDI1tB0cRymOX1A/27rTeG4AYAeQv+t/kX3Ig/MDPY4nF89eVv7FEzDJEOAWPEKRniNzXEyyBAnstxxrR6m7m/SoMjVGpJc+w= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=rdKU3Ex0; arc=none smtp.client-ip=209.85.128.46 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="rdKU3Ex0" Received: by mail-wm1-f46.google.com with SMTP id 5b1f17b1804b1-4a17baef589so27224105e9.0 for ; Fri, 16 Oct 2026 03:57:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1792148275; x=1792753075; darn=lists.linux.dev; h=content-transfer-encoding:content-type:mime-version:references :in-reply-to:message-id:date:subject:cc:to:from:from:to:cc:subject :date:message-id:reply-to:content-type; bh=JjoY/Y//bNqM95eGJvwXGt/YGARtJeL2jF1lkb5NGWs=; b=rdKU3Ex0BJB3RKleH37Jpa5Od03LCfCIAFW/iQcsXbyqjMJ5EVpVB9LKCjDKRn5+aq bYaVIp3Xsn4bVi0WeriwZG8eZYNYX68UXwJsA0NvCnn9losA/n4bBTqNV3WgeWaWw2uC oXe52PRlQxx/urS5KIM3wY6XLwBw7caVov62Kt2fEdiYnrZAMXFXilIbl/Z8mGZNvVTJ +m2t7Q8UzeR5guqhXMN3qOMiehCxunmYrN+YINobbbZGidoWJ/VH6ImzFW65Yz13Qt5L xNLAaM5hkneSN8YBmfrPVWtooDjyuBdGU0BwHDyUvWhrEcczyWH5tWInrmeLMIhjD2vF 6etA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20260707; t=1792148275; x=1792753075; h=content-transfer-encoding:content-type:mime-version:references :in-reply-to:message-id:date:subject:cc:to:from:x-gm-gg :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to :content-type; bh=JjoY/Y//bNqM95eGJvwXGt/YGARtJeL2jF1lkb5NGWs=; b=E+Qh7USu8OweNdZs1rD9yXnWpHJD4yVa/P1U4mkuXQqhgKZmB1wFX9A/qI0WWjAEjn L0O+ZiXkF5yfMG3XBZH3kjzTV4qjV8nqFjLzbux1Ools7XNIJ1Qiyvi3hys+KbakIam+ /ycBmXXXF2NAJKotniGNcX1e27S/xmF/AKmkxEjJu8qp275F4Sx6MMsNm3l64f5A2N57 C4kPbw7o6T/+pwmm7fdcoVLlxPDltPWYoEYZVtL1Zyo0/9zHNkIOusArFccRjUQGDNNQ 6M27h3C0VDg4iXl39M/Mt3DRQDZ5N6j7bWR1JdunoE4KKn0iCpgj/vPyv2hBQ8kT0/vv zpUQ== X-Forwarded-Encrypted: i=1; AKwUvBxdSd8NoaIwd+erjCPeGE1FXTr5VcqIuLK1GcE1C9TIgeTMO0w0DHxebZEz/UM9/C6ztFEerA==@lists.linux.dev X-Gm-Message-State: AFq9FYL0OyfakadHfU9oqB5HeUSCH9k0MEfh5Ed6K1T/XrXOpC1brs+h k3xC7OmXqdkv510sJ1llmWp+8xREfQfMVL+Itq8dOfqUvSpE7IPYLYVh X-Gm-Gg: AYBFou0K8fBi/omULuSz44yIlPSICDAu/Bv3IMx8yb+vCXb9g+EO//vxygacMq3Hey9 RaSuSOXaCVESA9RDS29XSJgd4tPNM/JjA5ZiKBRoopnjzlVIxjG0pmlH0Kp2Q/ZFCECNAkwVrJp nsceJ4hqOc0fOKJc+xW60GSchIT6u1QtUXtmvkKRM5xTeq1yIGyXQ6eGmr/JmsQ3fq3xh8dpFjP PD74dzwg+eHsOuGWFfWhILqK+qV0N+Uyy2x9Tr+tXpPvMP0LW9lbSW22De5QE5gToEItn3zpbG2 eO/H+zu/4vBzyYC1pnyRbsN251zv9kLFUGiVRdJXuWXwKTwmNoCTupWfx2bRlt0Gp7pUKaBtBMN /Wz8IHV+VBotplBM0KkNnxVdDASA1j3+SeSmwBp9gWINON0VQO6FD78kK7qbBwyjztKFTPqzetw IvBYOHarDbpWAejj2FyxIzyWE5eR8xsGuMihhGd1kLlL7pNhnFT3zG5aCxn4PCccjHoyRd0AT2d Vlt5o0oStz74btj9gVgtAK2ck00TXPaaEY5CO/0jVThthPlmbyVf3KzBvNqYN28TZWypAfKBIaW 4YFu6RfCUV255IqOYzl6xdOyn2QusUltAGg= X-Received: by 2002:a05:600d:82c8:b0:4a1:cedc:ab51 with SMTP id 5b1f17b1804b1-4a1cedcac09mr30065765e9.35.1792148274917; Fri, 16 Oct 2026 03:57:54 -0700 (PDT) Received: from dev-dsk-fgriffo-1c-93421965.eu-west-1.amazon.com (54-240-197-234.amazon.com. [54.240.197.234]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-4a1c8ae6d2esm50003685e9.6.2026.10.16.03.57.53 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Oct 2026 03:57:54 -0700 (PDT) From: Fred Griffoul To: Paolo Bonzini , Sean Christopherson , Marc Zyngier , Oliver Upton , Catalin Marinas , Andrew Morton , David Hildenbrand , Alexander Viro , Christian Brauner , Jan Kara , Jason Gunthorpe , Kevin Tian , Joerg Roedel , Will Deacon , Robin Murphy , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H . Peter Anvin" , Jonathan Corbet , Shuah Khan , Shuah Khan , "Aneesh Kumar K . V" Cc: David Woodhouse , Ackerley Tng , Lorenzo Stoakes , "Liam R . Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , Joey Gouly , Suzuki K Poulose , Zenghui Yu , Steffen Eiden , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org, linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [RFC PATCH v2 00/11] mm: Memory providers for guest_memfd and iommufd Date: Fri, 16 Oct 2026 10:57:52 +0000 Message-ID: <20261016105752.68015-1-griffoul@gmail.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: References: <20261014093733.90312-1-griffoul@gmail.com> Precedence: bulk X-Mailing-List: iommu@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Aneesh Kumar K.V writes: > What confused me was the introduction of memory providers as a subsystem > in their own. What we really need is the ability to map PFNs from > other subsystems into KVM stage-2 and into subsystems such as iommufd?. > > Restricting the scope to the above, at least initially, would make this > much easier to reason about. Thanks for looking at it. I should have explained this better in the cover letter. A memory provider is the driver that owns some memory, like a carve-out or a device BAR. It lends pages to whoever maps them, and it can take any of them back later. guest_memfd is one user of that memory, and iommufd is another, but neither depends on the other. With this series, iommufd can map a provider file without any VM. Today it cannot map such memory, because memory without struct page cannot be pinned. For example, a host service that recycles provider memory between VMs could clear it with a DMA engine driven through VFIO and iommufd, instead of the CPU. And since such memory can outlive the process, or a kexec of the host, a network or storage dataplane could restart or be updated without losing its DMA buffers. > For my use case, the VFIO fd becomes the backing provider (referred to > as backend below). We can create a guest_memfd using that > resource_fd, allowing MMIO BAR ranges to be mapped into KVM stage-2. That fits well. VFIO could be a provider for its BARs: get_page() reports the BAR frames with the MMIO type. guest_memfd takes the VFIO fd as resource_fd, and iommufd can map the same fd. That could also replace the dma-buf plus symbol_get() path that iommufd uses for vfio-pci today. > Another feature provided by this series is the ability to map the same > range into iommufd. We probably want to restrict this to shared ranges. > It may be simpler for guest_memfd to drive this. Agreed that guest_memfd must drive shared and private. I replied to Ackerley on how that could work with the provider interface: https://lore.kernel.org/all/20261015171746.51538-1-griffoul@gmail.com/ In short, on a conversion to private, guest_memfd claims the range on the provider file. The provider code in mm then revokes it for every other consumer, iommufd included, and hands them holes until guest_memfd unclaims it. So guest_memfd stays in charge of conversions, and iommufd only ever maps shared pages, without going through guest_memfd. > Currently, a private-to-shared conversion causes a VM exit, followed by > an IOAS_MAP for the newly shared range. Could using guest_memfd with > IOAS_MAP_FILE avoid this? Yes, the IOAS_MAP goes away. The conversion itself still comes through the VMM, but once guest_memfd unclaims the range, iommufd maps the pages again on its own. > Perhaps the series could be rearranged as follows: > > - Allow a guest_memfd fd to be used with IOAS_MAP_FILE. > - Add a VFIO or other backend for guest_memfd, without calling it a provider. > - Add support for guest_memfd to provide guest PFNs to other subsystems > through its file descriptor. I'd rather not make guest_memfd the only way in. With kvm_gmem_ops, each backend implements a guest_memfd: it binds memslots, invalidates KVM's mappings, handles the host mapping, and for confidential VMs prepares the frames and gives them back to the host. That puts KVM internals in every driver. With a provider, the driver only reports its frames and revokes them, and guest_memfd does the KVM side once, for every provider. Your diagram already uses mem_provider_ops between guest_memfd and iommufd. It is the same interface: get the frame behind a page, and revoke a range. So I'd define it once and let drivers use it too. That also covers the cases above, where there is no VM and no guest_memfd to go through. guest_memfd can still provide its own file to iommufd where there is no provider behind it, for a guest_memfd that allocates folios. That would use the same interface, and the same iommufd code. Would that work for your VFIO case? Thanks, Fred