From: John Levon <levon@movementarian.org>
To: Horst von Brand <brand@jupiter.cs.uni-dortmund.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/4] oprofile update: CPU type as string
Date: Tue, 11 Feb 2003 12:42:14 +0000 [thread overview]
Message-ID: <20030211124214.GA63656@compsoc.man.ac.uk> (raw)
In-Reply-To: <200302111234.h1BCYqgS004257@eeyore.valparaiso.cl>
On Tue, Feb 11, 2003 at 01:34:52PM +0100, Horst von Brand wrote:
> Better use "ia32/P4" and so on, "i386/P4" makes little sense ;-)
It's modelled after linux/arch/<blah>
> You could (should?) place the CPU ID into the model spec too...
eh ?
> BTW, if nobody (except masochistic kernel source readers) sees this stuff,
> what is the point? An enum uses less space than a char * + the string.
The type is used by the userspace to determine what counters are
available.
john
next prev parent reply other threads:[~2003-02-11 12:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-11 11:32 [PATCH 1/4] oprofile update: Pentium IV support John Levon
2003-02-11 11:42 ` [PATCH 2/4] oprofile update: CPU type as string John Levon
2003-02-11 12:34 ` Horst von Brand
2003-02-11 12:42 ` John Levon [this message]
2003-02-11 11:43 ` [PATCH 3/4] oprofile update: fix oprofilefs integer files base John Levon
2003-02-11 11:45 ` [PATCH 4/4] oprofile update: kernel/user addresses fix John Levon
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=20030211124214.GA63656@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=brand@jupiter.cs.uni-dortmund.de \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome