| 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
| ||
|
Date: Thu, 26 Jun 2008 16:03:31 +0800 From: "Huang, Ying" <ying.huang@...el.com> To: Yinghai Lu <yhlu.kernel@...il.com> Cc: "H. Peter Anvin" <hpa@...or.com>, andi@...stfloor.org, mingo@...hat.com, tglx@...utronix.de, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/2] x86 boot: early_res_to_e820 On Thu, 2008-06-26 at 00:29 -0700, Yinghai Lu wrote: [...] > > > > For example, if EFI memory map is allocated in highmem area by > > boot-loader, it need to be reserved in kernel. But on i386, bootmem can > > only reserve memory area below max_low_pfn. So I think this is needed. > > > > In general, I think it is needed to provide a reservation mechanism for > > highmem area on i386. Because some memory area from BIOS or boot-loader > > may in highmem area. > > I mean call reserve_setup_data right after finish_e820_parsing, and > it could call e820_update_range directly. e820_update_range() can only be used after finish_e820_parsing()? parse_setup_data() should be called before parse_early_param() to let early_param override settings in setup_data. Which is before finish_e820_parsing(). It seems a little wired to use the data before reserve it. And this means find_e820_area() should not be called before e820_update_range()? Best Regards, Huang Ying -- 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