From: Dean Nelson <dcn@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] move cnodeid_to_nasid_table out of pda
Date: Tue, 22 Mar 2005 12:37:58 +0000 [thread overview]
Message-ID: <20050322123758.GA12064@sgi.com> (raw)
In-Reply-To: <423F2342.mailxGRL11RVD3@aqua.americas.sgi.com>
On Mon, Mar 21, 2005 at 08:42:58PM -0800, Christoph Lameter wrote:
> > On Mon, 21 Mar 2005, Dean Nelson wrote:
> >
> > > Another step in the effort to eliminate the SN pda structure.
> > > This patch moves the cnodeid_to_nasid_table field out of the pda,
> > > making it a standalone per-cpu data item, and exports it so it can
> > > be accessed by kernel modules.
>
> Yuck something went wrong with the test. Turns out that I need a lot more
> definitions to make mmtimer a module since it uses the SHUB access macros.
> The following patch applies on top of Dean's patch:
You're missing a patch from Jack Steiner that basically does what you
are trying to do in this patch. Jack's patch can be found at:
http://lia64.bkbits.net:8080/linux-ia64-test-2.6.12
and is about 14 days old entitled:
[IA64-SGI] [PATCH 2/2] - New chipset support for SN platform
In this patch he moved the following fields out of the pda and into their
own per-cpu data structure called sn_hub_info_s, the pointer to which is
exported.
- u16 nasid_bitmask;
- u8 shub2;
- u8 nasid_shift;
- u8 as_shift;
- u8 shub_1_1_found;
I suggest you get that patch.
I'm also in the process of creating a patch to separate the nodepda from
the pda and export the phys_cpuid array of structures. This will allow
modules to use cpuid_to_nasid(cpuid).
prev parent reply other threads:[~2005-03-22 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-21 19:40 [PATCH] move cnodeid_to_nasid_table out of pda Dean Nelson
2005-03-22 2:03 ` Christoph Lameter
2005-03-22 4:42 ` Christoph Lameter
2005-03-22 12:37 ` Dean Nelson [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=20050322123758.GA12064@sgi.com \
--to=dcn@sgi.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