From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Stephane Eranian <eranian@hpl.hp.com>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
perfmon@napali.hpl.hp.com, linux-kernel@vger.kernel.org
Subject: Re: [perfmon] Re: cpuinfo_x86 and apicid
Date: Thu, 6 Jul 2006 15:47:11 -0700 [thread overview]
Message-ID: <20060706154711.C13512@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060706223745.GD10760@frankl.hpl.hp.com>; from eranian@hpl.hp.com on Thu, Jul 06, 2006 at 03:37:45PM -0700
On Thu, Jul 06, 2006 at 03:37:45PM -0700, Stephane Eranian wrote:
> Suresh,
>
> On Thu, Jul 06, 2006 at 03:25:43PM -0700, Stephane Eranian wrote:
> > >
> > Ah, yes I missed that. It works there two. I had something wrong
> > about how I accessed cpu_data. I am used to the elegant way we
> > do it on IA-64 but on x86_64 you have to index the cpu_data[]
> > array with smp_processor_id(). I was pointing to cpu_data[0]
> > on all processors.
> >
> > For what I need, I can do cpuinfo_x86->apicid & 0x3 to identify
> > which thread is running. I can now remove some more code in perfmon2.
> >
> I meant cpuinfo_x86->apicid & 0x1.
Instead of hard coding, can you get the size of the mask runtime from the
size of cpu_sibling_map[cpu]
And remember, physical/logical hotplug can change this sibling map.
thanks,
suresh
prev parent reply other threads:[~2006-07-06 22:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 15:01 cpuinfo_x86 and apicid Stephane Eranian
2006-07-06 15:27 ` linux-os (Dick Johnson)
2006-07-06 16:19 ` Siddha, Suresh B
2006-07-06 20:00 ` Stephane Eranian
2006-07-06 21:06 ` Siddha, Suresh B
2006-07-06 22:25 ` Stephane Eranian
2006-07-06 22:37 ` [perfmon] " Stephane Eranian
2006-07-06 22:47 ` Siddha, Suresh B [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=20060706154711.C13512@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=eranian@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perfmon@napali.hpl.hp.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