diff options
| author | Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com> | 2012-08-21 11:02:51 +0800 |
|---|---|---|
| committer | Avi Kivity <avi@redhat.com> | 2012-08-22 15:09:03 +0300 |
| commit | 4d8b81abc47b83a1939e59df2fdb0e98dfe0eedd (patch) | |
| tree | 47ea77cb4f77a2884a0478ecf84f62e32e5661ee /net | |
| parent | 7068d0971524dd47a38f44f6020ba133432871ca (diff) | |
KVM: introduce readonly memslot
In current code, if we map a readonly memory space from host to guest
and the page is not currently mapped in the host, we will get a fault
pfn and async is not allowed, then the vm will crash
We introduce readonly memory region to map ROM/ROMD to the guest, read access
is happy for readonly memslot, write access on readonly memslot will cause
KVM_EXIT_MMIO exit
Signed-off-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions