| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 22 Aug 2012 15:09:35 +0300 From: Avi Kivity <avi@...hat.com> To: Xiao Guangrong <xiaoguangrong@...ux.vnet.ibm.com> CC: Marcelo Tosatti <mtosatti@...hat.com>, LKML <linux-kernel@...r.kernel.org>, KVM <kvm@...r.kernel.org> Subject: Re: [PATCH v6 00/12] KVM: introduce readonly memslot On 08/21/2012 05:57 AM, Xiao Guangrong wrote: > Changelog: > - fix endless retrying for unhandleable instruction which accesses on readonly > host memory > - divide slot->flags by 16:16, the lower part is visible for userspace, the > reset is internally used in kvm, and document this in the code > - check slot->flags for gfn_to_hva_memslot > > The test case can be found at: > http://lkml.indiana.edu/hypermail/linux/kernel/1207.2/00819/migrate-perf.tar.bz2 > > 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. > > As Avi's suggestion, 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. Thanks, applied 1-11. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists