linux-kernel - Re: [patch 6/6] Guest page hinting: s390 support.

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]

Message-ID: <47D953AB.1030901@goop.org>
Date:	Thu, 13 Mar 2008 09:17:47 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	schwidefsky@...ibm.com
CC:	akpm@...l.org, linux-s390@...r.kernel.org, frankeh@...son.ibm.com,
	nickpiggin@...oo.com.au, linux-kernel@...r.kernel.org,
	virtualization@...ts.osdl.org,
	Anthony Liguori <anthony@...emonkey.ws>, hugh@...itas.com
Subject: Re: [patch 6/6] Guest page hinting: s390 support.

Jeremy Fitzhardinge wrote:
> Martin Schwidefsky wrote:
>> Vz->Vr cannot happen. This would be a bug in the host.
>>   
>
> Does that mean that Vz is effectively identical to Uz? 

Hm, on further thought:

If guests writes to Vz pages are disallowed, then the only way out of Vz 
is if the guest sets it to something else (Uz,Sz).  If so, what's the 
point of using that state?  Why not make:

    Vr -> Uz      host discard
    Pr -> Uz      host discard clean
    Sp -> Uz      set volatile
    Uz -> Uz      set volatile

But given how you've described V-state pages, I really would expect 
writes to a Vz to work, or alternatively, all writes to V-state pages to 
be disallowed.  Are there any real uses for a writable Vr page?

On the other hand, removing Vz->Vr does clean up the dot graph a lot...

    J

View attachment "gph.dot" of type "text/plain" (1309 bytes)

Download attachment "gph.pdf" of type "application/pdf" (16517 bytes)