From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1LhVBB-0007o4-IH for mharc-grub-devel@gnu.org; Wed, 11 Mar 2009 16:37:29 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LhVB9-0007kT-FZ for grub-devel@gnu.org; Wed, 11 Mar 2009 16:37:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LhVB7-0007hK-TV for grub-devel@gnu.org; Wed, 11 Mar 2009 16:37:27 -0400 Received: from [199.232.76.173] (port=39210 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LhVB7-0007hA-Qe for grub-devel@gnu.org; Wed, 11 Mar 2009 16:37:25 -0400 Received: from fk-out-0910.google.com ([209.85.128.186]:48446) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LhVB7-0005aN-AR for grub-devel@gnu.org; Wed, 11 Mar 2009 16:37:25 -0400 Received: by fk-out-0910.google.com with SMTP id 19so79180fkr.10 for ; Wed, 11 Mar 2009 13:37:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=6YYge8dvV9hGnG6lkQp0N41a7l7Rr0+E4Ozgbf6purE=; b=geGLsjEIlqMabfDPF9nYU3QOcm4a/L4HdkGycGaZZelPjG8kgXgZq3w9aUG8bnd65F yexLgDdUG2lS7CkNh+QReiwonkYlwLukbTUvs2X2LzOJ2qiA98UUdSpXwI52i+NUmcoy NZEXyx7vKI10zn5dsgHZ/wer3Zsh6xqbedyTA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=Jtyls0hZkaVz5IO1KLQRP/UHIH+vk2YmmA5/webRkXr6Y+Byr+OOBp1vKGyGFNJ1m5 9XPz1oSqc4I68t+v//I+q62VHlmB4zF4xTolau8CuhMONfDn2XHaNrFipvASnXcL07Dl uIkV52gT3r7+MEmNH+ePFXKYODuAyWhhxQbIY= Received: by 10.223.126.66 with SMTP id b2mr6772653fas.3.1236803842640; Wed, 11 Mar 2009 13:37:22 -0700 (PDT) Received: from ?192.168.1.2? (44-46.3-85.cust.bluewin.ch [85.3.46.44]) by mx.google.com with ESMTPS id 35sm300538fkt.23.2009.03.11.13.37.21 (version=SSLv3 cipher=RC4-MD5); Wed, 11 Mar 2009 13:37:22 -0700 (PDT) Message-ID: <49B82102.5010109@gmail.com> Date: Wed, 11 Mar 2009 21:37:22 +0100 From: phcoder User-Agent: Thunderbird 2.0.0.19 (X11/20090105) MIME-Version: 1.0 To: The development of GRUB 2 References: <20090227194253.GA31474@thorin> <49B66393.2040301@gmail.com> <49B6A789.3080600@gmail.com> In-Reply-To: <49B6A789.3080600@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: Re: [PATCH] badram filtering 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: Wed, 11 Mar 2009 20:37:27 -0000 Hello. I'm now writing the code to make multiboot and bsd work on EFI based on my grub_machine_memory_iterate for EFI. MY code will be the same for all i386 branches. It's quite complete except that I had no time yet to test it. I'l submit once it works I was thinking and found another utility for badram: BIOS hooks. They are actually allocating take some memory and then removing it from mmap. If bios mmap hook and kernels get their mmap from the same source we can ensure that bios hooks won't be overwritten by the kernel independently how it acquired memory map. So I think badram patch should be extended to allow arbitrary additions to mmap. P.S. sorry if this e-mail isn't clear enough I've just had a long day of studies phcoder wrote: >> 2) when badram variable is set corresponding memory chunks should be >> removed from memory manager >> 3) add a method to specify badram in init.c so that grub2 itself has >> no risk of using any of this memory. I propose to embed initial >> environment in core.img. Then prefix and root can be changed to use >> this mechanism. It would also be able to override this initial >> environment through multiboot command line when grub2 is loaded by >> multiboot loader >> >> >> Robert Millan wrote: >>> Hi, >>> >>> This patch implements badram filtering in GRUB. It's the same idea >>> as in >>> http://rick.vanrein.org/linux/badram/ but applied to GRUB. >>> >>> The badram module sits between loaders (or other users like lsmmap) and >>> filters the mmap entries, but only when user previously set the "badram" >>> variable (whose syntax is the same as the one in badram patch for >>> Linux). >>> >>> NOTE this won't affect loadees that get the memory map from BIOS instead >>> of from GRUB. This means it currently works for Multiboot and for the >>> new/experimental Linux loader. >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Grub-devel mailing list >>> Grub-devel@gnu.org >>> http://lists.gnu.org/mailman/listinfo/grub-devel >> >> > > -- Regards Vladimir 'phcoder' Serbinenko