From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] SAL_MC_RENDEZ logic
Date: Thu, 06 Feb 2003 12:02:27 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805820@msgid-missing> (raw)
2.4.20-ia64-021210/arch/ia64/kernel/mca.c::ia64_mca_rendez_int_handler
/* Register with the SAL monarch that the slave has
* reached SAL
*/
ia64_sal_mc_rendez();
/* Wait for the wakeup IPI from the monarch
* This waiting is done by polling on the wakeup-interrupt
* vector bit in the processor's IRRs
*/
ia64_mca_wakeup_ipi_wait();
The documentation for SAL_MC_RENDEZ (24535901.pdf) says that SAL itself
spins, looking for the wakeup ipi. Why is the kernel code doing the
same work? Either SAL_MC_RENDEZ does not spin (and the SAL docs are
wrong) or the kernel code in ia64_mca_wakeup_ipi_wait is redundant.
Why do I care? I am trying to get kdb/lcrash data after MCA.
reply other threads:[~2003-02-06 12:02 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=marc-linux-ia64-105590709805820@msgid-missing \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.