From: Stan Shebs <stan@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Command for number of cores
Date: Mon, 02 Aug 2010 15:17:00 -0000 [thread overview]
Message-ID: <4C56E170.5090103@codesourcery.com> (raw)
In-Reply-To: <AANLkTi=O8vbh1+2LDPvb7PO=MLxWPg2ondc179OESA7u@mail.gmail.com>
Doug Evans wrote:
> I hesitate to add "info cores" because it seems a bit esoteric, and
> you'd have to hack gdb, gdbserver, and document it all when "remote
> get" could suffice.
>
How about an "info arch cores"? We have "info os <x>" that is
extensible in a OS-specific way, but I would think number of cores is
more a property of the architecture than of the OS (although they do
interact).
Curious that we don't have an "info arch" already - have we really never
needed random arch info before?
Stan
prev parent reply other threads:[~2010-08-02 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 19:55 Marc Khouzam
2010-07-28 2:05 ` Hui Zhu
2010-07-28 19:02 ` Marc Khouzam
2010-07-29 2:21 ` Hui Zhu
2010-08-02 0:38 ` Marc Khouzam
2010-07-28 19:50 ` Doug Evans
2010-07-29 20:27 ` Marc Khouzam
2010-08-02 15:17 ` Stan Shebs [this message]
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=4C56E170.5090103@codesourcery.com \
--to=stan@codesourcery.com \
--cc=dje@google.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
/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