Re: SVSM Development Call July 2nd, 2025
Jörg Rödel <[email protected]> Wed, 9 Jul 2025 14:02:22 +0200
| Newsgroups | dev.linux.lists.coconut-svsm,dev.linux.lists.linux-coco |
|---|---|
| Message-ID | <dxk7tpe3sebmv55p2izpwe5nr5esqf7rxwtzzmjio5zmzogam4@mdtstwmhvyj2> |
Hi Richard, On Tue, Jul 08, 2025 at 10:12:09AM -0500, Relph, Richard wrote: > Jon Lange should weigh in here... he's the expert on this. > But I believe it would need to be dynamic at run-time. > Using 'worst case' allocations that might have every page ending up needing > it's own page state entry leads to excessive memory reservations. While not > having enough memory leads to fatal errors. Being able start with a > "reasonable" amount for page state while allowing for expansion later if > needed is the preferred solution. At least that's what I was hearing last > Wednesday. I think it is reasonable to assume that the (Linux) guest will eventually use all available memory, and thus it makes sense to allocate the page-state tracking data structure(s) big enough to cover all all guest memory right from the start. This eliminates the need for runtime resizing of SVSM memory, which is also only possible on platforms/configurations that use the SVSM protocol. Regards, Joerg