From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23898 invoked by alias); 29 Aug 2002 22:58:05 -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 23890 invoked from network); 29 Aug 2002 22:58:04 -0000 Received: from unknown (HELO walton.kettenis.dyndns.org) (62.163.169.250) by sources.redhat.com with SMTP; 29 Aug 2002 22:58:04 -0000 Received: from elgar.kettenis.dyndns.org (elgar.kettenis.dyndns.org [192.168.0.2]) by walton.kettenis.dyndns.org (8.12.5/8.12.5) with ESMTP id g7TMvQJt000405; Fri, 30 Aug 2002 00:57:26 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: from elgar.kettenis.dyndns.org (localhost [127.0.0.1]) by elgar.kettenis.dyndns.org (8.12.5/8.12.5) with ESMTP id g7TMvQq8000446; Fri, 30 Aug 2002 00:57:26 +0200 (CEST) (envelope-from kettenis@elgar.kettenis.dyndns.org) Received: (from kettenis@localhost) by elgar.kettenis.dyndns.org (8.12.5/8.12.5/Submit) id g7TMvOCb000443; Fri, 30 Aug 2002 00:57:24 +0200 (CEST) To: Eli Zaretskii Cc: Andrew Cagney , gdb-patches@sources.redhat.com Subject: Re: [rfc] Query Red Boot's i386 CPU id References: From: Mark Kettenis Date: Thu, 29 Aug 2002 16:01:00 -0000 In-Reply-To: Eli Zaretskii's message of "Thu, 29 Aug 2002 08:24:20 +0300 (IDT)" Message-ID: <86bs7lp92j.fsf@elgar.kettenis.dyndns.org> X-SW-Source: 2002-08/txt/msg01018.txt.bz2 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 :-). Mark