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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 30 Mar 2010 16:32:25 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Xiao Guangrong <xiaoguangrong@...fujitsu.com>
CC:	Ingo Molnar <mingo@...e.hu>, Marcelo Tosatti <mtosatti@...hat.com>,
	Sheng Yang <sheng@...ux.intel.com>,
	KVM list <kvm@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] KVM MMU: thinking of shadow page cache

On 03/30/2010 04:59 AM, Xiao Guangrong wrote:
> When we cached shadow page tables, one guest page table may have
> many shadow pages, take below case for example:
>
>   (RO+U) --->  |------| __     |------|
>   (W+U ) --->  |  GP1 |   |    |  GP2 |
>   (W+P ) --->  |------|   |-->  |------|
>
> There have 3 kinds of permission mapping to GP1, so we should
> allocate 3 shadow pages for GP1 and 3 shadow pages for GP2.
> And it has 3 class permissions(R/W, U/S, X/NX) in x86's architecture,
> for the worst case, we should allocate 2^3 pages for every paging
> mapping level.
>
> This waste is caused by that we only set the permission bits in PTE,
> not in the middle mapping level.
>
> So, i think we can mapping guest page table's permission into cache
> shadow page table, then it can be shared between many shadow page tables
> if their map to the same gust physics address. For above case, we only need 2
> pages.
>
> Any comments?
>    

We've considered this in the past, it makes sense.  The big question is 
whether any guests actually map the same page table through PDEs with 
different permissions (mapping the same page table through multiple PDEs 
is very common, but always with the same permissions).  Do you know of 
any such guest?

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ