Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: Eli Zaretskii <eliz@is.elta.co.il>,
	Andrew Cagney <ac131313@ges.redhat.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [rfc] Query Red Boot's i386 CPU id
Date: Thu, 29 Aug 2002 16:44:00 -0000	[thread overview]
Message-ID: <20020829233828.GA29966@nevyn.them.org> (raw)
In-Reply-To: <86bs7lp92j.fsf@elgar.kettenis.dyndns.org>

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 <eliz@is.elta.co.il> 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


  reply	other threads:[~2002-08-29 23:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-28 15:20 Andrew Cagney
2002-08-29  0:08 ` Eli Zaretskii
2002-08-29 16:01   ` Mark Kettenis
2002-08-29 16:44     ` Daniel Jacobowitz [this message]
2002-08-30 12:10     ` Eli Zaretskii
2002-08-30  6:52   ` Michal Ludvig
2002-08-29 17:30 ` Daniel Jacobowitz
2002-08-30 13:08   ` Andrew Cagney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020829233828.GA29966@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@ges.redhat.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kettenis@chello.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox