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 respin 1] MCA/INIT: tweaks
Date: Sun, 11 Sep 2005 03:47:13 +0000	[thread overview]
Message-ID: <22319.1126410433@ocs3.ocs.com.au> (raw)
In-Reply-To: <22055.1126409801@ocs3.ocs.com.au>

On Sun, 11 Sep 2005 13:36:41 +1000, 
Keith Owens <kaos@sgi.com> wrote:
>Respin 1 of the tweaks to the previous MCA/INIT patch sets.
>
>* Remove the requirement that kernel stacks be aligned on KERNEL_STACK_SIZE.
>* Remove the serialization of MCA/INIT handlers returning to SAL.  The
>  problem looked like a race but was really caused by a broken prom
>  doing cacheable accesses to the minstate area.
>* Print the cpu number and monarch status in the INIT handler.
>* Workaround for broken proms that access the minstate area using
>  cacheable addresses.
>* Remove the export of the scheduler hooks until we have modular code
>  that needs them.
>* Remove the final reference to MINSTATE_VIRT.
>* Workaround for broken proms that drive all INIT events as slaves.
>* Workaround for broken proms that drive all INIT events as monarchs.

Tony, that is all the changes that I have planned for the (fast
approaching) 2.6.14-rc1.  The scheduler hooks have already been posted
to linux-kernel for discussion[1], the patch got just one query which
has been answered.

Do you want me to reissue a new complete patch set or are you happy
with appending the tweaks to the existing patch set?  Whatever is
easier for your git tree.

[1] http://lkml.org/lkml/2005/9/8/315/


      reply	other threads:[~2005-09-11  3:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-11  3:36 [PATCH 2.6.13 8/7 respin 1] MCA/INIT: tweaks Keith Owens
2005-09-11  3:47 ` 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=22319.1126410433@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