From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9376 invoked by alias); 29 Aug 2002 23:37:23 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 9369 invoked from network); 29 Aug 2002 23:37:22 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 29 Aug 2002 23:37:22 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 17kZn0-0006rZ-00; Thu, 29 Aug 2002 19:37:30 -0500 Received: from drow by nevyn.them.org with local (Exim 3.35 #1 (Debian)) id 17kYrs-0007oy-00; Thu, 29 Aug 2002 19:38:28 -0400 Date: Thu, 29 Aug 2002 16:44:00 -0000 From: Daniel Jacobowitz To: Mark Kettenis Cc: Eli Zaretskii , Andrew Cagney , gdb-patches@sources.redhat.com Subject: Re: [rfc] Query Red Boot's i386 CPU id Message-ID: <20020829233828.GA29966@nevyn.them.org> Mail-Followup-To: Mark Kettenis , Eli Zaretskii , Andrew Cagney , gdb-patches@sources.redhat.com References: <86bs7lp92j.fsf@elgar.kettenis.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86bs7lp92j.fsf@elgar.kettenis.dyndns.org> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-08/txt/msg01020.txt.bz2 On Fri, Aug 30, 2002 at 12:57:24AM +0200, Mark Kettenis wrote: > I haven't looked at the patch too closely yet but: > > Eli Zaretskii writes: > > > > - a command to query the cpuid (info cpu). > > > > > > The actual CPU information is determined using a small file database > > > (installed in ..../share/gdb/i386-cpuid). > > > > > > Comments on how this was implemented, and what, if anything, could be > > > integrated into GDB, welcome. > > > > A few comments: > > > > (1) Why is this feature implemented for remote targets only? Why is > > the database of CPU ids installed only for embedded builds? > > Seconded. I'm getting wild ideas of downloading the cpuid code to the > target, executing it there, and fetching the return value, and use > that to e.g. select whether it makes sense to do MMX or SSE :-). [Makes me a little nervous to randomly execute code on the target... have you ever accidentally (or deliberately!) connected the wrong arch gdb?] I'm against the separate database file however. Can we generate a C table from it, the way we do other data? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer