[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231123003513.24292-1-ankita@nvidia.com>
Date: Thu, 23 Nov 2023 06:05:08 +0530
From: <ankita@...dia.com>
To: <ankita@...dia.com>, <jgg@...dia.com>,
<alex.williamson@...hat.com>, <naoya.horiguchi@....com>,
<akpm@...ux-foundation.org>, <tony.luck@...el.com>, <bp@...en8.de>,
<linmiaohe@...wei.com>, <rafael@...nel.org>, <lenb@...nel.org>,
<james.morse@....com>, <shiju.jose@...wei.com>,
<bhelgaas@...gle.com>, <pabeni@...hat.com>, <yishaih@...dia.com>,
<shameerali.kolothum.thodi@...wei.com>, <kevin.tian@...el.com>
CC: <aniketa@...dia.com>, <cjia@...dia.com>, <kwankhede@...dia.com>,
<targupta@...dia.com>, <vsethi@...dia.com>, <acurrid@...dia.com>,
<apopple@...dia.com>, <anuaggarwal@...dia.com>,
<jhubbard@...dia.com>, <danw@...dia.com>, <mochs@...dia.com>,
<kvm@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <linux-mm@...ck.org>,
<linux-edac@...r.kernel.org>, <linux-acpi@...r.kernel.org>
Subject: [PATCH v2 0/4] mm: Implement ECC handling for pfn with no struct page
From: Ankit Agrawal <ankita@...dia.com>
The kernel MM currently handles ECC errors / poison only on memory page
backed by struct page. As part of [1], the nvgrace-gpu-vfio-pci module
maps the device memory to user VA (Qemu) using remap_pfn_range without
being added to the kernel. These pages are not backed by struct page.
Implement a new ECC handling for memory without struct pages. Kernel MM
expose registration APIs to allow modules that are managing the device
to register its memory region and a callback function. MM then tracks
such regions using interval tree.
The mechanism is largely similar to that of ECC on pfn with struct pages.
If there is an ECC error on a pfn, MM uses the registered memory failure
callback function to notify the module of the faulty PFN, so that the
module may take any required action. The pfn is then unmapped in Stage-2.
When the VM tries to access the page, it gets trapped in KVM, which calls
the vm ops fault function. If the module fault function returns
VM_FAULT_HWPOISON, KVM sends a BUS_MCEERR_AR to the usermode (Qemu) mapped
to the poisoned page.
Lastly, nvgrace-gpu-vfio-pci module make use of the new mechanism to get
poison handling support on the device memory.
Patch generated over v6.7-rc2 and with [1] applied. [1] is currently under
review.
[1] https://lore.kernel.org/all/20231114081611.30550-1-ankita@nvidia.com/
Signed-off-by: Ankit Agrawal <ankita@...dia.com>
---
Link for v1: https://lore.kernel.org/all/20230920140210.12663-1-ankita@nvidia.com/
v1 -> v2
- Change poisoned page tracking from bitmap to hashtable.
- Addressed miscellaneous comments in v1.
Ankit Agrawal (4):
mm: handle poisoning of pfn without struct pages
mm: Add poison error check in fixup_user_fault() for mapped pfn
mm: Change ghes code to allow poison of non-struct pfn
vfio/nvgpu: register device memory for poison handling
drivers/acpi/apei/ghes.c | 12 +--
drivers/vfio/pci/nvgrace-gpu/main.c | 123 ++++++++++++++++++++++-
drivers/vfio/vfio_main.c | 3 +-
include/linux/memory-failure.h | 22 +++++
include/linux/mm.h | 1 +
include/ras/ras_event.h | 1 +
mm/Kconfig | 1 +
mm/gup.c | 2 +-
mm/memory-failure.c | 146 +++++++++++++++++++++++-----
virt/kvm/kvm_main.c | 6 ++
10 files changed, 278 insertions(+), 39 deletions(-)
create mode 100644 include/linux/memory-failure.h
--
2.17.1
Powered by blists - more mailing lists