public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Dean Nelson <dcn@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 1/4] SGI Altix cross partition functionality
Date: Tue, 10 Aug 2004 19:54:00 +0000	[thread overview]
Message-ID: <20040810195400.GA11858@sgi.com> (raw)
In-Reply-To: <20040616163339.GA27891@sgi.com>

On Sat, Jul 31, 2004 at 07:46:23AM -0500, Robin Holt wrote:
> On Fri, Jul 30, 2004 at 03:15:35PM -0700, Luck, Tony wrote:
> > Dean> The question is whether we export ia64_sal and sal_lock? Or change these
> > Dean> inline functions to no longer be inline, move them to a new file (sn_sal.c),
> > Dean> and export the individual function names?
> > 
> > Dean> From my point of view the first solution is better from the standpoint of
> > Dean> the diagnostics folks who write tests that need to make SAL calls. It doesn't
> > Dean> seem appropriate that the linux kernel be the repository of a bunch of ad hoc
> > Dean> and miscellaneous SAL wrapper functions that no one but the diagnostics folks
> > Dean> use.
> > 
> > Dean> I would like to know your opinions on the direction to go with this.
> > 
> > This looks like a lesser of two evils decision.  On balance I think
> > that I'd prefer not to open up the floodgates for modules to make
> > arbitrary SAL calls ... so I'd prefer to see you un-inline and
> > export the functions that you need. "sn_sal.c" sounds a plausible
> > name for a file to house these functions.
> 
> This leaves our diags people with a fairly difficult position.
> They have some online diags which need to excercise parts of the shub.
> Those activities are currently coded in the PROM (make online and offline
> diags a lot more consistent) executed via SAL calls.
> 
> Would you be alright with changing the inlines into real functions,
> but still exporting the ia64_sal symbol as well?
> 
> Will you accept the online diags people sending sal call additions that
> no kernel component will ever use?  Will that policy remain consistent
> into the future?  This makes our job much more difficult as we move
> toward not having our own kernel at all, but using standard distribution
> kernels as they will always lag the community in merging back changes
> made to the ia64 tree.  Again, that argues for having the ia64_sal
> exported.  Please consider those needs when making your decision.

Tony,

I'm interested in your response to what Robin wrote. Care to comment?

And just another data point: we no longer need the sal_lock exported,
just ia64_sal, does this affect your thoughts on this matter?

Thanks,
Dean


  parent reply	other threads:[~2004-08-10 19:54 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
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 [this message]
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=20040810195400.GA11858@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