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 07:01:21 +0000 [thread overview]
Message-ID: <10873.1126162881@kao2.melbourne.sgi.com> (raw)
In-Reply-To: <10631.1126162398@kao2.melbourne.sgi.com>
On Thu, 08 Sep 2005 16:53:18 +1000,
Keith Owens <kaos@sgi.com> wrote:
>Some 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.
With the above tweaks, the new MCA/INIT handlers pass all my stress
tests. On SGI systems I can send INIT tens of times without any
problem, the system dumps the tasks and keeps going. I was also
running ia64regcheck at the same time, it passed the test, no registers
were corrupted by INIT.
All the problems that have been reported against the new MCA/INIT
handlers have been caused by SAL not conforming to the SAL
specification. Some versions of SAL only call the monarch cpu and not
the slaves for INIT. Some versions of SAL call all cpus as monarchs.
Some versions of SAL do not resume correctly after INIT. Even on these
broken versions of SAL, the new OS handlers give better results that
the existing OS handlers. On working versions of SAL, INIT is now
fully recoverable. On working versions of SAL, a recoverable MCA which
needs to send INIT in order to rendezvous can now be successfully
resumed.
This code is definitely ready for inclusion in 2.6.13-rc1.
next prev parent reply other threads:[~2005-09-08 7:01 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 [this message]
2005-09-08 7:10 ` Keith Owens
2005-09-08 20:35 ` Luck, Tony
2005-09-08 23:08 ` Keith Owens
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=10873.1126162881@kao2.melbourne.sgi.com \
--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