linux-kernel - Re: [Xen-devel] [PATCH 0/2] xen: Switch to virtual mapped linear p2m list

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, 28 Oct 2014 14:04:00 +0100
From:	Juergen Gross <jgross@...e.com>
To:	David Vrabel <david.vrabel@...rix.com>,
	Andrew Cooper <andrew.cooper3@...rix.com>,
	Ian Campbell <Ian.Campbell@...rix.com>
CC:	boris.ostrovsky@...cle.com, xen-devel@...ts.xensource.com,
	linux-kernel@...r.kernel.org
Subject: Re: [Xen-devel] [PATCH 0/2] xen: Switch to virtual mapped linear
 p2m list

On 10/28/2014 01:39 PM, David Vrabel wrote:
> On 28/10/14 12:07, Juergen Gross wrote:
>>
>> Okay, back to the original question: is the (up to) 64 MB virtual
>> mapping of the p2m list on 32-bit pv domains a problem or not?
>
> I think up-to 64 MiB of vmalloc area is fine.  The vmalloc space can be
> increased with a command line option in the unlikely event that there
> are domUs that would be affected.

Okay.

>
>> If yes, the virtual mapped linear p2m list could still be used on
>> 64 bit domains, paving the way for support of more than 512 GB of
>> domain memory. OTOH having to keep the p2m tree coding alive isn't
>> my favorite solution...
>
> Having to keep both the tree and linear p2m code would be awful.  Let's
> not do this!

Agreed. :-)


Juergen

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