On 9/28/26 11:24 AM, Scott Lurndal wrote:
Paul Clayton <paaronclayton@gmail.com> writes:[snip]
I have a personal dislike of nested page tables and some
Care to elaborate? As someone who worked with hypervisors
both before and after AMD introduced nested page tables,
I have nothing good to say about the alternatives to
NPT.
Nested page tables are necessarily wasteful of storage and
add latency.
I am inclined (likely from ignorance) to prefer
paravirtualization. For a new architecture, forcing all OSes
to use the architected (paravirtualization) interface may
not be entirely impractical.
(For an existing ISA with existing OSes, a transition to
paravirtualization would seem to require limited binary
translation.)
Paravirtualization does have problems. Nested virtualization,
where a host OS treats a guest OS as an application, does not
seem to fit this model well. On the other hand, application-
level code could (in theory?) directly interact with the
architected hypervisor, though I suspect such would cause
responsibility tracking headaches.
I know extremely little about virtualization, but the
obvious inefficiency of nested page tables bothers me.
(Nested page tables may be the best selection when--- Synchronet 3.22a-Linux NewsLink 1.2
considering all the tradeoffs even for a new architecture.
The arguments that I have read focus on compatibility/
invisibility, which tends to exclude paravirtualization.)
Nested page tables also work around some page coalescing
issues (base physical pages can be mapped to large virtual
physical pages), though if such is not very common something
like Shadow Memory ("Increasing TLB Reach Using Superpages
Backed by Shadow Memory", Mark Swanson et al., 1998) might
be used to provide a limited amount of "double translated"
pages.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:48:48 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,582 |