-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for Sierra port #43
Open
dongahn
wants to merge
10
commits into
LLNL:master
Choose a base branch
from
dongahn:ibm_spectrum
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Commits on Mar 19, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 0846a0e - Browse repository at this point
Copy the full SHA 0846a0eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 5758b46 - Browse repository at this point
Copy the full SHA 5758b46View commit details -
Configuration menu - View commit details
-
Copy full SHA for 572f45d - Browse repository at this point
Copy the full SHA 572f45dView commit details -
launchmon: Add IBM Spectrum and PowerLE support
Adjust for OpenPower ABI functional call convension change: The ABI adds two different entry points, one for intramodule call and the other intermodule call (being done through TOC). Port for IBM Spectrum jsrun. Add new spectrum definition and also adjust back end deamon code as to how it should synchronize itself with Spectrum MPI target. Adjust how to handle new thread creation. When a new thread is created, we will get the SIGTRAP notification via waitpid on the parent thread that spawns a new thread. But on a recent Linux kernal, we have to check the high order bits of waitpid returned status as: leftshift status by 8 bits and then to see if it is equal to (SIGTRAP | (LINUX_TRACER_EVENT_CLONE << 8). Add a work around for jsrun's broken MPIR_attach_fifo. It is expecting ASCII 1 to be sent to the FIFO when it should expect a numeric 1. Need to drop it when IBM ultimately fixes the issue. (Bug filed to IBM).
Configuration menu - View commit details
-
Copy full SHA for c32febe - Browse repository at this point
Copy the full SHA c32febeView commit details -
Configuration menu - View commit details
-
Copy full SHA for baefbba - Browse repository at this point
Copy the full SHA baefbbaView commit details -
Remove BG deadwoods from test programs Add misaligned header comments Refactor printing of launcher path
Configuration menu - View commit details
-
Copy full SHA for 8d0c9c6 - Browse repository at this point
Copy the full SHA 8d0c9c6View commit details -
engine: Remove an MPIR_attach_fifo work-around
jsrun had a bug where MPIR_attach_fifo is expecting a byte that contains an ASCII '1' (49) when it should expect a byte that contains integer 1. The specification is at https://www.mpi-forum.org/docs/mpir-specification-10-11-2010.pdf
Configuration menu - View commit details
-
Copy full SHA for 97c8ee6 - Browse repository at this point
Copy the full SHA 97c8ee6View commit details -
engine: Add a warning note for RM designers
Warn about a common bug where the target RM process cannot detect the FIFO poke. When launchmon send integer 1 to the FIFO while the RM process is still stopped, the sent can go undetected even when the RM process resumes its execution depending on how the FIFO is polled.
Configuration menu - View commit details
-
Copy full SHA for 0e32013 - Browse repository at this point
Copy the full SHA 0e32013View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0576760 - Browse repository at this point
Copy the full SHA 0576760View commit details -
Configuration menu - View commit details
-
Copy full SHA for f75344d - Browse repository at this point
Copy the full SHA f75344dView commit details
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.