From: Dean Nelson <dcn@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 1/4] SGI Altix cross partition functionality
Date: Thu, 15 Jul 2004 12:47:52 +0000 [thread overview]
Message-ID: <20040715124752.GA19900@sgi.com> (raw)
In-Reply-To: <20040616163339.GA27891@sgi.com>
On Wed, Jul 14, 2004 at 11:01:08AM -0500, Dean Nelson wrote:
> On Wed, Jun 16, 2004 at 05:39:44PM +0100, Christoph Hellwig wrote:
> > On Wed, Jun 16, 2004 at 11:33:39AM -0500, Dean Nelson wrote:
> > > #include <asm/page.h>
> > > #include <asm/sal.h>
> > > #include <asm/pal.h>
> > >
> > > spinlock_t sal_lock __cacheline_aligned = SPIN_LOCK_UNLOCKED;
> > > +EXPORT_SYMBOL(sal_lock);
> >
> > No. Please don't make random sal calls from modules.
>
> We're only making one sal call (i.e., SN_SAL_GET_PARTITION_ADDR) to get the
> address of a partition's reserved page.
To be more precise, this is the only direct sal call we are making (i.e.,
using the SAL_CALL() macro directly). We are also making the following
indirect sal calls via the following wrappers, all of which are defined as
inline functions in include/asm-ia64/sn/sn_sal.h:
sn_register_nofault_code()
sn_change_memprotect()
sn_register_xp_addr_region()
sn_local_partid()
sn_partition_serial_number_val()
So I'll create a wrapper like these for the one remaining direct SAL_CALL()
we are making.
Being that they are all inline functions that call SAL_CALL() (one calls
SAL_CALL_NOLOCK()) still requires the exporting of sal_lock and ia64_sal.
Does all of this sound okay to you?
Thanks,
Dean
next prev parent reply other threads:[~2004-07-15 12:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 16:33 [PATCH 1/4] SGI Altix cross partition functionality Dean Nelson
2004-06-16 16:39 ` Christoph Hellwig
2004-06-16 17:20 ` Jesse Barnes
2004-06-16 17:28 ` Christoph Hellwig
2004-06-16 17:40 ` Robin Holt
2004-06-16 17:43 ` Christoph Hellwig
2004-06-16 19:36 ` Robin Holt
2004-07-14 16:01 ` Dean Nelson
2004-07-14 16:04 ` Dean Nelson
2004-07-15 12:47 ` Dean Nelson [this message]
2004-07-15 20:58 ` Christoph Hellwig
2004-07-15 21:00 ` Christoph Hellwig
2004-07-15 21:16 ` Jack Steiner
2004-07-29 16:10 ` Dean Nelson
2004-07-30 22:15 ` Luck, Tony
2004-07-31 12:46 ` Robin Holt
2004-08-10 19:54 ` Dean Nelson
2004-08-12 15:10 ` Dean Nelson
2004-08-23 16:50 ` Dean Nelson
2004-08-23 17:10 ` Dean Nelson
2004-08-23 17:51 ` Christoph Hellwig
2004-08-23 17:52 ` Christoph Hellwig
2004-08-23 19:16 ` Dean Nelson
2004-09-14 18:58 ` [PATCH 1/4] SGI Altix cross partition functionality (1st revision) Dean Nelson
2004-10-21 8:59 ` Christoph Hellwig
2004-10-21 11:01 ` Dean Nelson
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=20040715124752.GA19900@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