From: Richard Gooch <rgooch@ras.ucalgary.ca>
To: Zach Brown <zab@zabbo.net>
Cc: pmhahn@titan.lahn.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpuid/msr + devfs
Date: Mon, 3 Sep 2001 14:51:55 -0600 [thread overview]
Message-ID: <200109032051.f83Kpt428276@vindaloo.ras.ucalgary.ca> (raw)
In-Reply-To: <20010903163448.A22633@erasmus.off.net>
In-Reply-To: <Pine.LNX.4.33.0108121020050.1068-100000@titan.lahn.de> <200109032007.f83K73H27504@vindaloo.ras.ucalgary.ca> <20010903163448.A22633@erasmus.off.net>
Zach Brown writes:
> > Better to have a central place which creates per-CPU directories,
> > which you can call into and grab a directory for a CPU.
>
> I talked with arjan and rmk about this when playing around with per cpu
> statistics stuff. Is the proc_cpu.c stuff in the patch useful?
>
> http://www.osdlab.org/sw_resources/cpustat/cpustat-2.4.7.pre5-1.diff
Well, it can be used as a guide for where things have to be patched.
It's not really suited to creating devfs directories which can be used
by random CPU drivers, since you're using an initcall.
However, the per-CPU structures you seem to be creating appears to be
a logical place to add a devfs entry. As part of the CPU detection
process, that entry should be initialised. Then drivers can simply
reference that entry.
Regards,
Richard....
Permanent: rgooch@atnf.csiro.au
Current: rgooch@ras.ucalgary.ca
prev parent reply other threads:[~2001-09-03 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-12 8:33 Philipp Matthias Hahn
2001-09-03 20:07 ` Richard Gooch
2001-09-03 20:34 ` Zach Brown
2001-09-03 20:51 ` Richard Gooch [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=200109032051.f83Kpt428276@vindaloo.ras.ucalgary.ca \
--to=rgooch@ras.ucalgary.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=pmhahn@titan.lahn.de \
--cc=zab@zabbo.net \
/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
all inboxes | Powered by JetHome®