From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1LqROf-0003Kj-Nu for mharc-grub-devel@gnu.org; Sun, 05 Apr 2009 08:24:21 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LqROd-0003Jr-4q for grub-devel@gnu.org; Sun, 05 Apr 2009 08:24:19 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LqROY-0003J8-9v for grub-devel@gnu.org; Sun, 05 Apr 2009 08:24:18 -0400 Received: from [199.232.76.173] (port=41408 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LqROY-0003J5-4D for grub-devel@gnu.org; Sun, 05 Apr 2009 08:24:14 -0400 Received: from mta-out.inet.fi ([195.156.147.13]:54255 helo=jenni1.inet.fi) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LqROX-000591-L6 for grub-devel@gnu.org; Sun, 05 Apr 2009 08:24:14 -0400 Received: from [192.168.1.102] (84.248.105.254) by jenni1.inet.fi (8.5.014) id 49D075A800490DA6 for grub-devel@gnu.org; Sun, 5 Apr 2009 15:24:10 +0300 Message-ID: <49D8A2E4.3030908@nic.fi> Date: Sun, 05 Apr 2009 15:24:04 +0300 From: =?UTF-8?B?VmVzYSBKw6TDpHNrZWzDpGluZW4=?= User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: The development of GRUB 2 X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: Quoted-Printable X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Subject: memory allocator enhancements... X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Apr 2009 12:24:19 -0000 Hi All, I have been thinking on how to improve memory allocator (thou hasn't got too much time lately to play with it) so it could aid in following scenarios: 1. Move VBE BIOS thunks or other code from kernel to actual driver - specially named segment that gets allocated to lowmem in order to call VBE BIOS extensions - These should be located right after kernel in lowmem - Seems to be a bit tricky to patch relocation info properly (at least this is what I was last debugging). Ideas are welcome. Perhaps my code was not just modified properly... 2. Allocate memory for BIOS extensions in order to support BIOS drive mapping and El Torito or what ever someone needs. - Probably need to make hole to memory map that is passed to OS so allocated memory needs to be at end of lowmem so no holes within low memory are present - Perhaps this should be only done at last step of boot process. Eg allocate first memory to high mem and then when boot decision has been made, then allocate to low mem and make necessary hooks 3. Load OS image at start of highmem. I do not remember which OS needed this thou... 4. Allocate memory for GRUB code/modules/data. This can be at end of highmem. Are there any other needs? So what does people feel about these changes. I am afraid if too much freedom is given it will make it complex... Thanks, Vesa J=C3=A4=C3=A4skel=C3=A4inen