linux-kernel - Re: brk patches..

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: <49AB4091.6060701@kernel.org>
Date:	Sun, 01 Mar 2009 18:12:33 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>,
	the arch/x86 maintainers <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>
Subject: Re: brk patches..

Jeremy Fitzhardinge wrote:
> H. Peter Anvin wrote:
>> Jeremy Fitzhardinge wrote:
>>  
>>> (To be specific: I reshape the guest e820 table so that it doesn't have
>>> memory in any forbidden areas of the host e820 table.  That may require
>>> moving the pseudo-physical address of pages into a new overflow e820
>>> entry, which would also require allocating pages for the p2m radix
>>> tree.)
>>>
>>>     
>>
>> Isn't that the domain builder's job?
>>   
> 
> No.  It just provides a flat memory map from 0-max_pfn.  I want to avoid
> the overlap between pseudo-phys and machine memory so that the resource
> manager doesn't get confused by overlapping ranges, and so that it
> places the pci window in the same place as native.

where will those mem allocator needed?

if it is used after finish_e820_parsing(), you could use find_e820_area()

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