From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Ip3o7-0005ZU-7m for mharc-grub-devel@gnu.org; Mon, 05 Nov 2007 10:24:07 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Ip3o5-0005Xo-4P for grub-devel@gnu.org; Mon, 05 Nov 2007 10:24:05 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Ip3o3-0005XU-JV for grub-devel@gnu.org; Mon, 05 Nov 2007 10:24:04 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Ip3o3-0005X9-Di for grub-devel@gnu.org; Mon, 05 Nov 2007 10:24:03 -0500 Received: from aybabtu.com ([69.60.117.155]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Ip3o3-0001Ne-4O for grub-devel@gnu.org; Mon, 05 Nov 2007 10:24:03 -0500 Received: from [192.168.10.6] (helo=thorin) by aybabtu.com with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1Ip3o1-0007ms-QZ for grub-devel@gnu.org; Mon, 05 Nov 2007 16:24:02 +0100 Received: from rmh by thorin with local (Exim 4.63) (envelope-from ) id 1Ip3nq-00016T-2U for grub-devel@gnu.org; Mon, 05 Nov 2007 16:23:50 +0100 Date: Mon, 5 Nov 2007 16:23:50 +0100 From: Robert Millan To: The development of GRUB 2 Message-ID: <20071105152349.GC3583@thorin> References: <13461040.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: free as in freedom X-Message-Flag: Microsoft discourages use of Outlook. X-Debbugs-No-Ack: true User-Agent: Mutt/1.5.13 (2006-08-11) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. Subject: Re: Grub Memory Map - Processor 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: Mon, 05 Nov 2007 15:24:05 -0000 On Mon, Oct 29, 2007 at 12:14:53PM -0500, Andrei E. Warkentin wrote: > Juan, > > You may use the CPUID instruction to correctly identify the processor > your code is executing on. GRUB does not provide such information as > part of the Multiboot info. Ah, uhm right. I was thinking in terms of GRUB internals rather than multiboot on my last reply. Sorry for the confusion :-/ If you're working on an OS kernel, just use CPUID instruction like Andrei said. You can see our cpuid command for an example on how to do it (license terms apply if you copy actual code). -- Robert Millan I know my rights; I want my phone call! What use is a phone call, if you are unable to speak? (as seen on /.)