linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alex Williamson <alex@shazbot.org>
To: <ankita@nvidia.com>
Cc: <vsethi@nvidia.com>, <jgg@nvidia.com>, <mochs@nvidia.com>,
	<jgg@ziepe.ca>, <skolothumtho@nvidia.com>, <linmiaohe@huawei.com>,
	<nao.horiguchi@gmail.com>, <cjia@nvidia.com>, <zhiw@nvidia.com>,
	<kjaju@nvidia.com>, <yishaih@nvidia.com>, <kevin.tian@intel.com>,
	<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-mm@kvack.org>
Subject: Re: [PATCH v2 0/2] Register device memory for poison handling
Date: Mon, 19 Jan 2026 13:38:05 -0700	[thread overview]
Message-ID: <20260119133805.49fa7b8d@shazbot.org> (raw)
In-Reply-To: <20260115202849.2921-1-ankita@nvidia.com>

On Thu, 15 Jan 2026 20:28:47 +0000
<ankita@nvidia.com> wrote:

> From: Ankit Agrawal <ankita@nvidia.com>
> 
> Linux MM provides interfaces to allow a driver to [un]register device
> memory not backed by struct page for poison handling through
> memory_failure.
> 
> The device memory on NVIDIA Grace based systems are not added to the
> kernel and are not backed by struct pages. So nvgrace-gpu module
> which manages the device memory can make use of these interfaces to
> get the benefit of poison handling. Make nvgrace-gpu register the device
> memory with the MM on open.
> 
> Moreover, the stubs are added to accommodate for CONFIG_MEMORY_FAILURE
> being disabled.
> 
> Patch 1/2 introduces stubs for CONFIG_MEMORY_FAILURE disabled.
> Patch 2/2 registers the device memory at the time of open instead of mmap.
> 
> Note that this is a reposting of an earlier series [1] which is partly
> (patch 1/3) merged to v6.19-rc4. This one addresses the leftover patching.
> Many thanks to Jason Gunthorpe (jgg@nvidia.com) and Alex Williamson
> (alex@shazbot.org) for valuable suggestions.
> 
> Link: https://lore.kernel.org/all/20251213044708.3610-1-ankita@nvidia.com/ [1]
> 
> Changelog:
> v2:
> - Fixed nit to cleanup nvgrace_gpu_vfio_pci_register_pfn_range
>   (Thanks Jiaqi Yan)
> Link: https://lore.kernel.org/all/20260108153548.7386-1-ankita@nvidia.com/ [v1]
> 
> Ankit Agrawal (2):
>   mm: add stubs for PFNMAP memory failure registration functions
>   vfio/nvgrace-gpu: register device memory for poison handling
> 
>  drivers/vfio/pci/nvgrace-gpu/main.c | 113 +++++++++++++++++++++++++++-
>  include/linux/memory-failure.h      |  13 +++-
>  2 files changed, 120 insertions(+), 6 deletions(-)
> 

Applied to vfio next branch for v6.20/7.0.  Thanks,

Alex


      parent reply	other threads:[~2026-01-19 20:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-15 20:28 ankita
2026-01-15 20:28 ` [PATCH v2 1/2] mm: add stubs for PFNMAP memory failure registration functions ankita
2026-01-15 20:28 ` [PATCH v2 2/2] vfio/nvgrace-gpu: register device memory for poison handling ankita
2026-01-15 21:20   ` Jiaqi Yan
2026-01-19 20:38 ` Alex Williamson [this message]

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=20260119133805.49fa7b8d@shazbot.org \
    --to=alex@shazbot.org \
    --cc=ankita@nvidia.com \
    --cc=cjia@nvidia.com \
    --cc=jgg@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=kevin.tian@intel.com \
    --cc=kjaju@nvidia.com \
    --cc=kvm@vger.kernel.org \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mochs@nvidia.com \
    --cc=nao.horiguchi@gmail.com \
    --cc=skolothumtho@nvidia.com \
    --cc=vsethi@nvidia.com \
    --cc=yishaih@nvidia.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