[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v4 0/7] Poisoned memory recovery on reboot
From: |
David Hildenbrand |
Subject: |
Re: [PATCH v4 0/7] Poisoned memory recovery on reboot |
Date: |
Wed, 8 Jan 2025 22:22:04 +0100 |
User-agent: |
Mozilla Thunderbird |
On 14.12.24 14:45, “William Roche wrote:
From: William Roche <willia.roche@oracle.com>
Hello David,
Hi!
Let me start reviewing today a bit (it's already late, and I'll continue
tomorrow.
Here is an new version of our code and an updated description of the
patch set:
> ---> This set of patches fixes several problems with hardware
memory errors
impacting hugetlbfs memory backed VMs and the generic memory recovery
on VM reset.
When using hugetlbfs large pages, any large page location being impacted
by an HW memory error results in poisoning the entire page, suddenly
making a large chunk of the VM memory unusable.
I assume the problem that will remain is that a running VM will still
lose that chunk (yet, we only indicate a single 4k page to the guest via
an injected MCE :( ).
So the biggest point of this patch set is really the recovery on reboot.
And as I am writing this, I realize that the series subject correctly
reflects that :)
--
Cheers,
David / dhildenb
- Re: [PATCH v4 0/7] Poisoned memory recovery on reboot,
David Hildenbrand <=