linux-kernel - Re: [patch 0/6] Guest page hinting version 7.

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:	Sun, 29 Mar 2009 16:20:24 +0200
From:	Martin Schwidefsky <schwidefsky@...ibm.com>
To:	Rik van Riel <riel@...hat.com>
Cc:	Dave Hansen <dave@...ux.vnet.ibm.com>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, virtualization@...ts.osdl.org,
	frankeh@...son.ibm.com, akpm@...l.org, nickpiggin@...oo.com.au,
	hugh@...itas.com
Subject: Re: [patch 0/6] Guest page hinting version 7.

On Fri, 27 Mar 2009 20:06:03 -0400
Rik van Riel <riel@...hat.com> wrote:

> Dave Hansen wrote:
> > On Fri, 2009-03-27 at 16:09 +0100, Martin Schwidefsky wrote:
> >> If the host picks one of the
> >> pages the guest can recreate, the host can throw it away instead of writing
> >> it to the paging device. Simple and elegant.
> > 
> > Heh, simple and elegant for the hypervisor.  But I'm not sure I'm going
> > to call *anything* that requires a new CPU instruction elegant. ;)
> 
> I am convinced that it could be done with a guest-writable
> "bitmap", with 2 bits per page.  That would make this scheme
> useful for KVM, too.

This was our initial approach before we came up with the milli-code
instruction. The reason we did not use a bitmap was to prevent the
guest to change the host state (4 guest states U/S/V/P and 3 host
states r/p/z). With the full set of states you'd need 4 bits. And the
hosts need to have a "master" copy of the host bits, one the guest
cannot change, otherwise you get into trouble.

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

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