From: Zoltan Menyhart <Zoltan.Menyhart@free.fr>
To: linux-ia64@vger.kernel.org
Subject: MCA: Should we always wake up the non-monarch CPUs?
Date: Tue, 21 Mar 2006 23:31:33 +0000 [thread overview]
Message-ID: <44208CD5.2010206@free.fr> (raw)
The MCA handler always releases the non-monarch CPUs from the
rendez-vous before returning to the SAL.
It is quite o.k. if the MCA has been recovered.
Yet, if the MCA cannot be recovered, what is the use of releasing
the non-monarch CPUs from the rendez-vous?
(It is much more easy to analyze the system state by use of some
"external intelligence" if the non-monarch CPUs cannot run after
an MCA for some considerably long time.)
As far as I can see in the flow chart of the MCA handling in the
SAL spec. (Dec. 2003, figure 4-6, page 61), it indicates that a
_typical_ MCA handler should wake up the non-monarch CPUs.
Do I interpret correctly the spec. saying it is not an obligation,
and the monarch CPU can return to the SAL and can request a reboot
without waking up the non-monarch CPUs?
Thanks,
Zoltan Menyhart
reply other threads:[~2006-03-21 23:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44208CD5.2010206@free.fr \
--to=zoltan.menyhart@free.fr \
--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