2019-02-21 17:56:23 +03:00
|
|
|
Known issues in NVMM, low priority in most cases.
|
|
|
|
|
|
|
|
|
|
====== KERNEL NVMM DRIVER ======
|
|
|
|
|
|
2019-04-21 09:48:37 +03:00
|
|
|
* 32bit-PAE guests can misbehave on Intel, because we need to manually
|
|
|
|
|
install the PDPTEs, and currently we don't do it. In practice they don't
|
|
|
|
|
misbehave because the emulator never has to interfere with CR3.
|
2019-02-21 17:56:23 +03:00
|
|
|
|
2020-05-21 00:05:21 +03:00
|
|
|
* AMD: we don't support VCPU_CONF_TPR, would be nice to.
|
2019-02-21 17:56:23 +03:00
|
|
|
|
2020-05-21 00:05:21 +03:00
|
|
|
* AMD: need to do comprehensive CPUID filtering.
|
2019-02-21 17:56:23 +03:00
|
|
|
|
2020-05-21 00:05:21 +03:00
|
|
|
* Intel: we have comprehensive CPUID filtering, but should we limit the highest
|
|
|
|
|
leaf?
|
2019-02-21 17:56:23 +03:00
|
|
|
|
|
|
|
|
====== LIBNVMM ======
|
|
|
|
|
|
|
|
|
|
* There are still a few twisted corner cases we don't handle in the instruction
|
|
|
|
|
emulator. For example if the guest makes an MMIO access relative to RSP, we
|
|
|
|
|
must base the GVA on %SS and not %DS. This is tiring, and in practice, no
|
|
|
|
|
guest is dumb enough to perform such accesses.
|
|
|
|
|
|
2020-05-21 00:05:21 +03:00
|
|
|
* Maybe the __areas should have a rwlock? I don't think Qemu unmaps memory
|
|
|
|
|
while VCPUs are running, but still.
|
