From 6ef2e50bac017f49c12207edb82f080e6bebf486 Mon Sep 17 00:00:00 2001
From: Moe Jette <jette1@llnl.gov>
Date: Mon, 23 Aug 2004 21:01:32 +0000
Subject: [PATCH] Adjust base context number so that all context numbers fall
 within the RMS context range. This avoid Elan intallation errors with both
 lowcontext and highcontext are not with this range. (gnats:482)

---
 src/plugins/switch/elan/qsw.c | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/src/plugins/switch/elan/qsw.c b/src/plugins/switch/elan/qsw.c
index 6865c526ead..96ae084dc8a 100644
--- a/src/plugins/switch/elan/qsw.c
+++ b/src/plugins/switch/elan/qsw.c
@@ -56,8 +56,17 @@
  *  want to include here since we are using the new
  *  version-nonspecific libelanctrl.
  *  (XXX: What is the equivalent in libelanctrl?)
+ *
+ * slurm/482: the elan USER context range is now split
+ *  into two segments, regular user context and RMS 
+ *  context ranges. Do not allow a context range
+ *  (lowcontext -- highcontext) to span these two segments,
+ *  as this will generate and elan initialization error
+ *  when MPI tries to attach to the capability. For now,
+ *  restrict SLURM's range to the RMS one (starting at 0x400)
+ * 
  */
-# define ELAN_USER_BASE_CONTEXT_NUM    0x020
+# define ELAN_USER_BASE_CONTEXT_NUM    0x400 /* act. RMS_BASE_CONTEXT_NUM */
 # define ELAN_USER_TOP_CONTEXT_NUM     0x7ff
 
 # define Version      cap_version
-- 
GitLab