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:	Thu, 23 Aug 2012 14:23:51 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Konrad Rzeszutek Wilk <konrad@...nel.org>
CC:	Jacob Shin <jacob.shin@....com>, X86-ML <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Yinghai Lu <yinghai@...nel.org>,
	Andreas Herrmann <andreas.herrmann3@....com>,
	Tejun Heo <tj@...nel.org>,
	Borislav Petkov <borislav.petkov@....com>,
	Dave Young <dyoung@...hat.com>,
	Chao Wang <chaowang@...hat.com>,
	Vivek Goyal <vgoyal@...hat.com>
Subject: Re: [PATCH 3/4] x86: Only direct map addresses that are marked as
 E820_RAM

On 08/23/2012 01:12 PM, Konrad Rzeszutek Wilk wrote:
>>
>> Okay... I think I need to grok that a bit better.  For memory
>> allocations, we probably should just use brk allocations, for
>> virtual space allocations it is called the fixmap for a reason (even
>> though the Xen people managed to break that on 32 bits, sigh!)
> 
> Can you rope me in on that? Was that added ooh years ago ?

Yeah, it dates back to the original paravirt work.

The issue is that Xen likes to live at the top of the virtual address
space, which is where the fixmap lives.  Suddenly the fixmap is no
longer at a fixed address, which was sort of the whole idea.

The problem is that on i386 there are very few unmovable boundaries left
in the virtual address space.  The only other one left, really, is at
the very beginning of kernel space.

At this point people's appetite for large changes on 32 bits is limited,
of course.

	-hpa


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