linux-kernel - Re: [PATCH] x86-64: improve e820_search

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:	Sat, 09 May 2009 23:43:26 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Jan Beulich <jbeulich@...ell.com>, mingo@...e.hu,
	tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86-64: improve e820_search_gap()

Andi Kleen wrote:
>> However, as far as querying SRAT, I don't like the idea of spreading the 
>> knowledge of the system memory map out between a bunch of different 
>> places, each of which have a little piece of the puzzle.  It puts a huge 
>> onus on the user to know what mechanisms are actually available, and 
>> really makes a shitty interface.
> 
> AFAIK another popular OS always combines mappings from all sources (e820,
> SRAT, PCI, PNP, ACPI etc.) in the query before allocating anything.
> Something like that might be a reasonable long term direction for Linux
> too, but it's probably also a can of worms to handle the conflicts
> between the various sources (e.g. e820 reserves a lot of things
> in other sources too). It would be a rather large change.
> Maybe that would handle the systems I thought of above.

You *always* have a conflict resolution policy... whether or not it is
explicit or accidental, and whether or not it is the result of merging
the data or just accessing multiple data sources is another matter.  It
might be hard to replicate an accidental policy in an explicit way, or
the accidental policy really might make no sense, which may mean
behavior changes.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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