From: Erdem Aktas <erdemaktas@google.com>
To: dave.hansen@intel.com
Cc: almasrymina@google.com, dave.hansen@linux.intel.com,
gthelen@google.com, jiaqiyan@google.com, juew@google.com,
linux-mm@kvack.org, naoya.horiguchi@nec.com, seanjc@google.com,
tony.luck@intel.com
Subject: Re: [RFC] Expose a memory poison detector ioctl to user space.
Date: Thu, 28 Apr 2022 09:15:51 -0700 [thread overview]
Message-ID: <20220428161551.722296-1-erdemaktas@google.com> (raw)
In-Reply-To: <fccd0784-4c58-453f-1f34-9d4038431531@intel.com>
> On 4/26/22 12:23, Jue Wang wrote:
> > On Tue, Apr 26, 2022 at 11:18 AM Dave Hansen <dave.hansen@intel.com> wrote:
> I shouldn't speak for Intel as a whole, but I'll give you my personal
> perspective.
>
> Right now, hosts can't scan TDX private memory, period. If you wanted
> to do scanning, the guest has to do it or you have to kill the guest and
> make the memory non-private.
Actually, afaiu, the host can read tdx private memory. This should NOT generate
#MC due to integrity/TD ownership but return a fixed value of "0"s. I do not
know if this will also trigger #MCs due to memory errors.
>
> Going forward, guest memory scanning could be accomplished by allowing
> the VMM to migrate guest pages. Let's say you want to scan page "A",
> you could move A->B and B->A. That would certainly touch the page.
> This would need to be implemented in the TDX module.
TDH.MEM.PAGE.RELOCATE should be able to migrate guest pages but I am not sure
if this would be feasible depending on how often we keep relocating pages.
next prev parent reply other threads:[~2022-04-28 16:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 16:34 Jue Wang
2022-04-26 15:40 ` Dave Hansen
2022-04-26 17:57 ` Jue Wang
2022-04-26 18:02 ` Jue Wang
2022-04-26 18:21 ` Dave Hansen
2022-04-26 19:25 ` Jue Wang
2022-04-26 19:52 ` Luck, Tony
2022-04-26 20:06 ` Jue Wang
2022-04-26 18:20 ` Dave Hansen
2022-04-26 19:23 ` Jue Wang
2022-04-26 19:39 ` Dave Hansen
2022-04-26 19:50 ` Jue Wang
2022-04-28 16:15 ` Erdem Aktas [this message]
2022-04-28 16:34 ` Dave Hansen
2022-04-29 19:46 ` Jue Wang
2022-04-29 21:10 ` Dave Hansen
2022-04-29 21:32 ` Jue Wang
2022-04-29 21:44 ` Jue Wang
2022-04-29 22:29 ` Dave Hansen
2022-04-29 22:53 ` Jue Wang
2022-05-02 15:30 ` Dave Hansen
2022-05-02 17:19 ` David Hildenbrand
2022-05-02 17:30 ` Jue Wang
2022-05-02 17:33 ` David Hildenbrand
2022-05-02 17:36 ` Jue Wang
2022-05-02 17:38 ` David Hildenbrand
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=20220428161551.722296-1-erdemaktas@google.com \
--to=erdemaktas@google.com \
--cc=almasrymina@google.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=gthelen@google.com \
--cc=jiaqiyan@google.com \
--cc=juew@google.com \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=seanjc@google.com \
--cc=tony.luck@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