RE: [RFC] Expose a memory poison detector ioctl to user space.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



One thing that would be relatively easy to do would be pre-allocate and pre-scan memory at guest creation:

1) Request to set up a guest with X GB memory
2) Allocate X GB
3) Zero it
4) Scan for poison
5) Map memory to guest and run the guest

Should work with TDX (because you scan while host still has control/access to the pages).

But this has issues if you have long-lived guests. Or want to overcommit memory so don't
really give a guest all the physical memory that it asks for.

-Tony




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux