From: Ashok Raj <ashok.raj@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch]:MC/MT enabling/identification for IA-64
Date: Fri, 25 Feb 2005 20:27:21 +0000 [thread overview]
Message-ID: <20050225122720.A9055@unix-os.sc.intel.com> (raw)
In-Reply-To: <01EF044AAEE12F4BAAD955CB7506494303077707@scsmsx401.amr.corp.intel.com>
On Fri, Feb 25, 2005 at 12:12:34PM -0800, Seth, Rohit wrote:
>
> Will following work:
>
> Physical id: Identifying the unique physical package id for LEU
The spec states that physical processor id or (die id) is not required
to be unique. Are you depending on this being unique?
also PAL_LOGICAL_TO_PHYSICAL states that num_log (or total number of logical
processors in this die) doesnt necessarily need to be cpp * tpc)
just fyi: even if the numbers might be the same in most cases, its possible
that they could be different, because one thread didnt boot due to some
failure)
> Core id: Identifying the unique core id on that specific physical
> package
> Siblings: Identifying the total number LEUs on that physical package.
>
> Siblings is the one that apps have already started using on i386.
>
> -rohit
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at [2]http://vger.kernel.org/majordomo-info.html
>
> References
>
> 1. mailto:davidm@napali.hpl.hp.com
> 2. http://vger.kernel.org/majordomo-info.html
--
Cheers,
Ashok Raj
next prev parent reply other threads:[~2005-02-25 20:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-16 19:19 [patch]:MC/MT enabling/identification for IA-64 Seth, Rohit
2005-02-18 23:41 ` David Mosberger
2005-02-22 18:24 ` Seth, Rohit
2005-02-25 1:27 ` David Mosberger
2005-02-25 2:22 ` Seth, Rohit
2005-02-25 6:11 ` David Mosberger
2005-02-25 20:12 ` Seth, Rohit
2005-02-25 20:27 ` Ashok Raj [this message]
2005-02-25 20:47 ` David Mosberger
2005-02-25 20:47 ` Seth, Rohit
2005-02-25 21:15 ` Seth, Rohit
2005-02-25 22:46 ` David Mosberger
2005-02-25 23:01 ` Seth, Rohit
2005-02-25 23:03 ` David Mosberger
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=20050225122720.A9055@unix-os.sc.intel.com \
--to=ashok.raj@intel.com \
--cc=linux-ia64@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