From: Ankit Agrawal <ankita@nvidia.com>
To: Alex Williamson <alex@shazbot.org>
Cc: Vikram Sethi <vsethi@nvidia.com>,
Jason Gunthorpe <jgg@nvidia.com>, Matt Ochs <mochs@nvidia.com>,
"jgg@ziepe.ca" <jgg@ziepe.ca>,
Shameer Kolothum <skolothumtho@nvidia.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linmiaohe@huawei.com" <linmiaohe@huawei.com>,
"nao.horiguchi@gmail.com" <nao.horiguchi@gmail.com>,
Neo Jia <cjia@nvidia.com>, Zhi Wang <zhiw@nvidia.com>,
Krishnakant Jaju <kjaju@nvidia.com>,
Yishai Hadas <yishaih@nvidia.com>,
"kevin.tian@intel.com" <kevin.tian@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH v1 3/3] vfio/nvgrace-gpu: register device memory for poison handling
Date: Sat, 13 Dec 2025 04:52:56 +0000 [thread overview]
Message-ID: <SA1PR12MB7199E3B570F2E05183532E52B0AFA@SA1PR12MB7199.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20251213084757.0e6089f7.alex@shazbot.org>
Thanks for the review, Alex!
Comments addressed in v2.
https://lore.kernel.org/all/20251213044708.3610-1-ankita@nvidia.com/
next prev parent reply other threads:[~2025-12-13 4:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 7:06 [PATCH v1 0/3] mm: fixup pfnmap memory failure handling ankita
2025-12-11 7:06 ` [PATCH v1 1/3] mm: fixup pfnmap memory failure handling to use pgoff ankita
2025-12-11 7:06 ` [PATCH v1 2/3] mm: add stubs for PFNMAP memory failure registration functions ankita
2025-12-11 7:06 ` [PATCH v1 3/3] vfio/nvgrace-gpu: register device memory for poison handling ankita
2025-12-12 23:47 ` Alex Williamson
2025-12-13 4:52 ` Ankit Agrawal [this message]
2025-12-11 20:11 ` [PATCH v1 0/3] mm: fixup pfnmap memory failure handling Andrew Morton
2025-12-11 23:14 ` Jason Gunthorpe
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=SA1PR12MB7199E3B570F2E05183532E52B0AFA@SA1PR12MB7199.namprd12.prod.outlook.com \
--to=ankita@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=alex@shazbot.org \
--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