From: Jue Wang <juew@google.com>
To: pizhenwei@bytedance.com
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"David Hildenbrand" <david@redhat.com>,
jasowang@redhat.com, LKML <linux-kernel@vger.kernel.org>,
"Linux MM" <linux-mm@kvack.org>,
mst@redhat.com,
"HORIGUCHI NAOYA(堀口 直也)" <naoya.horiguchi@nec.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 0/3] recover hardware corrupted page by virtio balloon
Date: Wed, 25 May 2022 13:16:34 -0700 [thread overview]
Message-ID: <CAPcxDJ5pduUyMA0rf+-aTjK_2eBvig05UTiTptX1nVkWE-_g8w@mail.gmail.com> (raw)
Some points to consider:
The injected MCE has _done_ the damages to guest workload. Recovering
the guest poisoned memory doesn't help with the already happened guest
workload memory corruption / loss / interruption due to injected MCEs.
The hypervisor _must_ emulate poisons identified in guest physical
address space (could be transported from the source VM), this is to
prevent silent data corruption in the guest. With a paravirtual
approach like this patch series, the hypervisor can clear some of the
poisoned HVAs knowing for certain that the guest OS has isolated the
poisoned page. I wonder how much value it provides to the guest if the
guest and workload are _not_ in a pressing need for the extra KB/MB
worth of memory.
Thanks,
-Jue
next reply other threads:[~2022-05-25 20:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 20:16 Jue Wang [this message]
2022-05-26 18:37 ` Peter Xu
2022-05-27 6:32 ` zhenwei pi
2022-05-30 7:41 ` David Hildenbrand
2022-05-30 11:33 ` zhenwei pi
2022-05-30 15:49 ` Peter Xu
2022-05-31 4:08 ` Jue Wang
2022-06-01 2:17 ` zhenwei pi
2022-06-01 7:59 ` David Hildenbrand
2022-06-02 9:28 ` zhenwei pi
2022-06-02 9:40 ` David Hildenbrand
-- strict thread matches above, loose matches on Subject: below --
2022-05-20 7:06 zhenwei pi
2022-05-24 18:59 ` David Hildenbrand
2022-05-27 3:47 ` zhenwei pi
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=CAPcxDJ5pduUyMA0rf+-aTjK_2eBvig05UTiTptX1nVkWE-_g8w@mail.gmail.com \
--to=juew@google.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mst@redhat.com \
--cc=naoya.horiguchi@nec.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=pizhenwei@bytedance.com \
--cc=qemu-devel@nongnu.org \
--cc=virtualization@lists.linux-foundation.org \
/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