From: Matthew Wilcox <willy@debian.org>
To: Grant Grundler <grundler@dsl2.external.hp.com>
Cc: "Michael S. Zick" <mszick@goquest.com>,
parisc-linux@lists.parisc-linux.org, mszick@MoreThan.org
Subject: Re: [parisc-linux] 2.4.18-pa35 SMP process hangs on a J200
Date: Fri, 14 Jun 2002 03:05:54 +0100 [thread overview]
Message-ID: <20020614030554.I9435@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20020613215246.3B1864848@dsl2.external.hp.com>; from grundler@dsl2.external.hp.com on Thu, Jun 13, 2002 at 03:52:46PM -0600
On Thu, Jun 13, 2002 at 03:52:46PM -0600, Grant Grundler wrote:
> > Additional note: On the HP models with the worst of the problems;
> > is the physical_cpu_id and the logical_cpu_id a 1:1 mapping as
> > it is on x86 systems?
>
> Yes. parisc didn't have a concept of physical CPU ID until
> PAT PDC (eg A500, N-class, etc). When we want to support
> CPU addition and removal, we can add physical/logical
> mappings and it will no longer be 1:1.
Actually this came up in an unrelated question today. I found that
where other architectures use a physical ID, we use an address. So we
really have no use for logical/physical mappings. When the CPU hotplug
code is introduced, it will actually remove the logical numbering and
loops over all cpus will be done with loops over all physical cpus and
a check to see whether that cpu is online.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-06-14 2:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 5:36 [parisc-linux] 2.4.18-pa35 SMP process hangs on a J200 Ryan Bradetich
2002-06-11 5:52 ` Randolph Chung
2002-06-11 8:08 ` Thibaut VARENE
2002-06-11 12:10 ` Michael S.Zick
2002-06-11 14:58 ` Randolph Chung
2002-06-11 15:04 ` John David Anglin
2002-06-11 18:39 ` Michael S.Zick
2002-06-12 13:45 ` Michael S.Zick
2002-06-13 21:52 ` Grant Grundler
2002-06-14 2:05 ` Matthew Wilcox [this message]
2002-06-12 14:11 ` Matthew Wilcox
2002-06-12 10:49 ` Thibaut VARENE
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=20020614030554.I9435@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=grundler@dsl2.external.hp.com \
--cc=mszick@MoreThan.org \
--cc=mszick@goquest.com \
--cc=parisc-linux@lists.parisc-linux.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