From: David Hildenbrand <david@redhat.com>
To: "“William Roche" <william.roche@oracle.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org, qemu-arm@nongnu.org
Cc: peterx@redhat.com, pbonzini@redhat.com,
richard.henderson@linaro.org, philmd@linaro.org,
peter.maydell@linaro.org, mtosatti@redhat.com,
imammedo@redhat.com, eduardo@habkost.net,
marcel.apfelbaum@gmail.com, wangyanan55@huawei.com,
zhao1.liu@intel.com, joao.m.martins@oracle.com
Subject: Re: [PATCH v6 3/6] accel/kvm: Report the loss of a large memory page
Date: Thu, 30 Jan 2025 18:02:55 +0100 [thread overview]
Message-ID: <ca2c2d71-e4c0-4ed2-afc0-04f21df1f82d@redhat.com> (raw)
In-Reply-To: <20250127213107.3454680-4-william.roche@oracle.com>
On 27.01.25 22:31, “William Roche wrote:
> From: William Roche <william.roche@oracle.com>
>
> In case of a large page impacted by a memory error, provide an
> information about the impacted large page before the memory
> error injection message.
>
> This message would also appear on ras enabled ARM platforms, with
> the introduction of an x86 similar error injection message.
>
> In the case of a large page impacted, we now report:
> Memory Error on large page from <backend>:<address>+<fd_offset> +<page_size>
>
> Signed-off-by: William Roche <william.roche@oracle.com>
> ---
> accel/kvm/kvm-all.c | 11 +++++++++++
> include/exec/cpu-common.h | 9 +++++++++
> system/physmem.c | 21 +++++++++++++++++++++
> target/arm/kvm.c | 3 +++
> 4 files changed, 44 insertions(+)
>
> diff --git a/accel/kvm/kvm-all.c b/accel/kvm/kvm-all.c
> index f89568bfa3..08e14f8960 100644
> --- a/accel/kvm/kvm-all.c
> +++ b/accel/kvm/kvm-all.c
> @@ -1296,6 +1296,17 @@ static void kvm_unpoison_all(void *param)
> void kvm_hwpoison_page_add(ram_addr_t ram_addr)
> {
> HWPoisonPage *page;
> + struct RAMBlockInfo rb_info;
> +
> + if (qemu_ram_block_location_info_from_addr(ram_addr, &rb_info)) {
> + size_t ps = rb_info.page_size;
> + if (ps > TARGET_PAGE_SIZE) {
> + uint64_t offset = ram_addr - rb_info.offset;
> + error_report("Memory Error on large page from %s:%" PRIx64
> + "+%" PRIx64 " +%zx", rb_info.idstr,
> + QEMU_ALIGN_DOWN(offset, ps), rb_info.fd_offset, ps);
> + }
> + }
Some smaller nits:
1) I'd call it qemu_ram_block_info_from_addr() -- drop the "_location"
2) Printing the fd_offset only makes sense if there is an fd, right?
You'd have to communicate that information as well.
Apart from that, this series LGTM, thanks!
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-01-30 17:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 21:31 [PATCH v6 0/6] Poisoned memory recovery on reboot “William Roche
2025-01-27 21:31 ` [PATCH v6 1/6] system/physmem: handle hugetlb correctly in qemu_ram_remap() “William Roche
2025-01-30 10:05 ` David Hildenbrand
2025-01-27 21:31 ` [PATCH v6 2/6] system/physmem: poisoned memory discard on reboot “William Roche
2025-01-30 10:08 ` David Hildenbrand
2025-01-27 21:31 ` [PATCH v6 3/6] accel/kvm: Report the loss of a large memory page “William Roche
2025-01-30 12:02 ` David Hildenbrand
2025-01-30 17:02 ` David Hildenbrand [this message]
2025-02-01 9:57 ` William Roche
2025-01-27 21:31 ` [PATCH v6 4/6] numa: Introduce and use ram_block_notify_remap() “William Roche
2025-01-27 21:31 ` [PATCH v6 5/6] hostmem: Factor out applying settings “William Roche
2025-01-27 21:31 ` [PATCH v6 6/6] hostmem: Handle remapping of RAM “William Roche
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=ca2c2d71-e4c0-4ed2-afc0-04f21df1f82d@redhat.com \
--to=david@redhat.com \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=marcel.apfelbaum@gmail.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=wangyanan55@huawei.com \
--cc=william.roche@oracle.com \
--cc=zhao1.liu@intel.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;
as well as URLs for NNTP newsgroup(s).