public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 2.6.13 8/7] MCA/INIT: tweaks
Date: Thu, 08 Sep 2005 23:08:34 +0000	[thread overview]
Message-ID: <19085.1126220914@ocs3.ocs.com.au> (raw)
In-Reply-To: <10631.1126162398@kao2.melbourne.sgi.com>

On Thu, 8 Sep 2005 13:35:10 -0700, 
"Luck, Tony" <tony.luck@intel.com> wrote:
>Keith Owens <kaos@sgi.com> wrote:
>>>This code is definitely ready for inclusion in 2.6.13-rc1.
>>
>>Of course that should be 2.6.14-rc1.
>
>I'm happy that the ia64 parts show a definite improvement on the
>buggy-SAL systems that I can test on.  I'll take your word that
>this runs fine on SN2.  The cleanups to minstate.h alone make this
>patch beautiful in my eyes :-)
>
>We need to go to linux-kernel to get some blessings for the
>changes to <linux/sched.h> and kernel/sched.c.  The very first
>question is likely to be: "Why are curr_task() and set_curr_task()
>exported?" They are only used in mca.c ... which can't be built
>as a module.

Tools like kgdb, kprobes and kdb need curr_task() to check if a task is
running on a cpu or not, those components can be modular.
set_curr_task() does not need to be exported, it is a hang over from
some early testing.  I'll respin the tweaks patch (number 8) to remove
the export of set_curr_task().


      parent reply	other threads:[~2005-09-08 23:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-08  6:53 [PATCH 2.6.13 8/7] MCA/INIT: tweaks Keith Owens
2005-09-08  7:01 ` Keith Owens
2005-09-08  7:10 ` Keith Owens
2005-09-08 20:35 ` Luck, Tony
2005-09-08 23:08 ` Keith Owens [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=19085.1126220914@ocs3.ocs.com.au \
    --to=kaos@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