From: chrisl@vmware.com
To: Robert Love <rml@tech9.net>
Cc: Dave Jones <davej@codemonkey.org.uk>,
akpm@digeo.com, linux-kernel@vger.kernel.org, "Nakajima,
Jun" <jun.nakajima@intel.com>,
"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: [PATCH] How to get number of physical CPU in linux from user space?
Date: Fri, 25 Oct 2002 13:03:18 -0700 [thread overview]
Message-ID: <20021025200318.GE1397@vmware.com> (raw)
In-Reply-To: <1035573689.730.3473.camel@phantasy>
Cool. That will work for me.
Thanks
Chris
On Fri, Oct 25, 2002 at 03:21:28PM -0400, Robert Love wrote:
> On Fri, 2002-10-25 at 15:13, Dave Jones wrote:
>
> > Should this be wrapped in a if (cpu_has_ht(c)) { } ?
> > Seems silly to be displaying HT information on non-HT CPUs.
>
> I am neutral, but is fine with me. It is just "cpu_has_ht", btw.
>
> Take two...
>
> This displays the physical processor id and number of siblings of each
> processor in /proc/cpuinfo.
>
> Robert Love
>
> .proc.c.swp |binary
> proc.c | 7 +++++++
> 2 files changed, 7 insertions(+)
>
> diff -urN linux-2.5.44/arch/i386/kernel/cpu/proc.c linux/arch/i386/kernel/cpu/proc.c
> --- linux-2.5.44/arch/i386/kernel/cpu/proc.c 2002-10-19 00:02:29.000000000 -0400
> +++ linux/arch/i386/kernel/cpu/proc.c 2002-10-25 15:18:03.000000000 -0400
> @@ -17,6 +17,7 @@
> * applications want to get the raw CPUID data, they should access
> * /dev/cpu/<cpu_nr>/cpuid instead.
> */
> + extern int phys_proc_id[NR_CPUS];
> static char *x86_cap_flags[] = {
> /* Intel-defined */
> "fpu", "vme", "de", "pse", "tsc", "msr", "pae", "mce",
> @@ -74,6 +75,12 @@
> /* Cache size */
> if (c->x86_cache_size >= 0)
> seq_printf(m, "cache size\t: %d KB\n", c->x86_cache_size);
> +#ifdef CONFIG_SMP
> + if (cpu_has_ht) {
> + seq_printf(m, "physical processor ID\t: %d\n", phys_proc_id[n]);
> + seq_printf(m, "number of siblings\t: %d\n", smp_num_siblings);
> + }
> +#endif
>
> /* We use exception 16 if we have hardware math and we've either seen it or the CPU claims it is internal */
> fpu_exception = c->hard_math && (ignore_irq13 || cpu_has_fpu);
>
next prev parent reply other threads:[~2002-10-25 19:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 18:54 Nakajima, Jun
2002-10-25 19:09 ` [PATCH] " Robert Love
2002-10-25 19:13 ` Dave Jones
2002-01-16 19:35 ` Pavel Machek
2002-10-25 19:21 ` Robert Love
2002-10-25 20:03 ` chrisl [this message]
2002-10-25 21:13 ` Alan Cox
2002-10-25 19:12 ` chrisl
2002-10-25 19:48 [PATCH] " Nakajima, Jun
2002-10-25 20:38 Nakajima, Jun
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=20021025200318.GE1397@vmware.com \
--to=chrisl@vmware.com \
--cc=akpm@digeo.com \
--cc=davej@codemonkey.org.uk \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=rml@tech9.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
Powered by JetHome