October 2015 - mpiwg-tools - mailman3.cels.anl.gov

Changes from Dresden to MPIR
by Jeff Squyres (jsquyres) 08 Oct '15

08 Oct '15

See https://github.com/mpiwg-tools/mpir/pull/1 -- Jeff Squyres jsquyres(a)cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/

1 0

Re: [mpiwg-tools] Meeting reminder Oct 8, 8:00 AM PDT
by Mohror, Kathryn 08 Oct '15

08 Oct '15

Hi all, Notes from the meeting are here: https://github.com/mpiwg-tools/tools-issues/wiki/Notes-2015-10-08 Kathryn _________________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA > -----Original Message----- > From: mpiwg-tools [mailto:[email protected]] On > Behalf Of Michael Knobloch > Sent: Thursday, October 8, 2015 7:32 AM > To: mpiwg-tools(a)lists.mpi-forum.org > Subject: Re: [mpiwg-tools] Meeting reminder Oct 8, 8:00 AM PDT > > Hi all, > > I won't be able to join today and Marc-Andre might be a couple of minutes > late as he missed the bus (though with the next one he still should be on > time). > > -Michael > > On 08.10.2015 10:26, Marc-Andre Hermanns wrote: > > Hi all, > > > >> This is your friendly reminder of our regular working group meeting > >> tomorrow at 8:00 AM PDT. The link to join the webex meeting is on our > wiki: > >> > >> https://github.com/mpiwg-tools/tools-issues/wiki/Meetings > >> > >> As far as agenda goes, I think we will mostly be talking about > >> debugger topics, since I know a few of the tools people will not be able to > join. > >> Let's discuss: > >> - Feedback to ticket #384 (aka issue #5) reading > >> - Possible topic: MPIR support for MPI implementations with > >> threads as MPI processes > > - Github (working group) workflows > > > > Cheers, > > Marc-Andre > > > > > > > > _______________________________________________ > > mpiwg-tools mailing list > > mpiwg-tools(a)lists.mpi-forum.org > > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools > > > > -- > Michael Knobloch > Institute for Advanced Simulation (IAS) > Jülich Supercomputing Centre (JSC) > Telefon: +49 2461 61-3546 > Telefax: +49 2461 61-6656 > E-Mail: m.knobloch(a)fz-juelich.de > Internet: http://www.fz-juelich.de/jsc > > > ---------------------------------------------------------------------------------------------- > -- > ---------------------------------------------------------------------------------------------- > -- > Forschungszentrum Juelich GmbH > 52425 Juelich > Sitz der Gesellschaft: Juelich > Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 > Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher > Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), > Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. > Sebastian M. Schmidt > ---------------------------------------------------------------------------------------------- > -- > ---------------------------------------------------------------------------------------------- > -- > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools

1 0

Re: [mpiwg-tools] Meeting reminder Oct 8, 8:00 AM PDT
by Michael Knobloch 08 Oct '15

08 Oct '15

Hi all, I won't be able to join today and Marc-Andre might be a couple of minutes late as he missed the bus (though with the next one he still should be on time). -Michael On 08.10.2015 10:26, Marc-Andre Hermanns wrote: > Hi all, > >> This is your friendly reminder of our regular working group meeting tomorrow >> at 8:00 AM PDT. The link to join the webex meeting is on our wiki: >> >> https://github.com/mpiwg-tools/tools-issues/wiki/Meetings >> >> As far as agenda goes, I think we will mostly be talking about debugger >> topics, since I know a few of the tools people will not be able to join. >> Let's discuss: >> - Feedback to ticket #384 (aka issue #5) reading >> - Possible topic: MPIR support for MPI implementations with threads as MPI >> processes > - Github (working group) workflows > > Cheers, > Marc-Andre > > > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools > -- Michael Knobloch Institute for Advanced Simulation (IAS) Jülich Supercomputing Centre (JSC) Telefon: +49 2461 61-3546 Telefax: +49 2461 61-6656 E-Mail: m.knobloch(a)fz-juelich.de Internet: http://www.fz-juelich.de/jsc ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------

1 0

Re: [mpiwg-tools] Meeting reminder Oct 8, 8:00 AM PDT
by Marc-Andre Hermanns 08 Oct '15

08 Oct '15

Hi all, > This is your friendly reminder of our regular working group meeting tomorrow > at 8:00 AM PDT. The link to join the webex meeting is on our wiki: > > https://github.com/mpiwg-tools/tools-issues/wiki/Meetings > > As far as agenda goes, I think we will mostly be talking about debugger > topics, since I know a few of the tools people will not be able to join. > Let's discuss: > - Feedback to ticket #384 (aka issue #5) reading > - Possible topic: MPIR support for MPI implementations with threads as MPI > processes - Github (working group) workflows Cheers, Marc-Andre -- Marc-Andre Hermanns Jülich Aachen Research Alliance, High Performance Computing (JARA-HPC) Jülich Supercomputing Centre (JSC) Schinkelstrasse 2 52062 Aachen Germany Phone: +49 2461 61 2509 | +49 241 80 24381 Fax: +49 2461 80 6 99753 www.jara.org/jara-hpc email: hermanns(a)jara.rwth-aachen.de

1 0

Meeting reminder Oct 8, 8:00 AM PDT
by Kathryn Mohror 07 Oct '15

07 Oct '15

Hi all, This is your friendly reminder of our regular working group meeting tomorrow at 8:00 AM PDT. The link to join the webex meeting is on our wiki: https://github.com/mpiwg-tools/tools-issues/wiki/Meetings As far as agenda goes, I think we will mostly be talking about debugger topics, since I know a few of the tools people will not be able to join. Let's discuss: - Feedback to ticket #384 (aka issue #5) reading - Possible topic: MPIR support for MPI implementations with threads as MPI processes Talk to you soon! Kathryn _________________________________________________________________ Kathryn Mohror, kathryn(a)llnl.gov, http://scalability.llnl.gov/ Scalability Team @ Lawrence Livermore National Laboratory, Livermore, CA, USA

1 0

Re: [mpiwg-tools] Issues workflow
by Bland, Wesley 05 Oct '15

05 Oct '15

To clarify, if you'll only be doing work within the working group and not making comments on tickets outside of the working group, notifying us is not required. That step is only if you want to make comments on tickets being considered by the full forum or participate in writing a ticket for the full forum. > On Oct 5, 2015, at 2:45 AM, Marc-Andre Hermanns <hermanns(a)jara.rwth-aachen.de> wrote: > > Dear all, > > Wes and Jeff put up a summary of the new issue (a.k.a ticket) workflow at: > > https://github.com/mpi-forum/mpi-issues/wiki/Issue-Workflow > > It all starts with anyone wanting to directly edit the text to create > an account on Github and let Wes or Jeff know. > > Be sure to read the guidelines at: > > https://github.com/mpi-forum/mpi-issues/wiki > > Cheers, > Marc-Andre > -- > Marc-Andre Hermanns > Jülich Aachen Research Alliance, > High Performance Computing (JARA-HPC) > Jülich Supercomputing Centre (JSC) > > Schinkelstrasse 2 > 52062 Aachen > Germany > > Phone: +49 2461 61 2509 | +49 241 80 24897 > Fax: +49 2461 80 6 99753 > www.jara.org/jara-hpc > email: hermanns(a)jara.rwth-aachen.de > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools

1 0

Issues workflow
by Marc-Andre Hermanns 05 Oct '15

05 Oct '15

Dear all, Wes and Jeff put up a summary of the new issue (a.k.a ticket) workflow at: https://github.com/mpi-forum/mpi-issues/wiki/Issue-Workflow It all starts with anyone wanting to directly edit the text to create an account on Github and let Wes or Jeff know. Be sure to read the guidelines at: https://github.com/mpi-forum/mpi-issues/wiki Cheers, Marc-Andre -- Marc-Andre Hermanns Jülich Aachen Research Alliance, High Performance Computing (JARA-HPC) Jülich Supercomputing Centre (JSC) Schinkelstrasse 2 52062 Aachen Germany Phone: +49 2461 61 2509 | +49 241 80 24897 Fax: +49 2461 80 6 99753 www.jara.org/jara-hpc email: hermanns(a)jara.rwth-aachen.de

1 0

Re: [mpiwg-tools] Prefix of PMPI replacement interface
by Martin Schulz 04 Oct '15

04 Oct '15

For what it¹s worth - after the last meeting I got some good ideas and I started designing and coding on the prototype again; and for now I started calling it the MPI Plugin interface (using the MPI_Plugin prefix) since it will be much more generic than hooks or a plain tools interface. I think this could grow into a very generic interface that can be use to fundamentally change the behavior and flavor of an MPI implementation by loading specific plugins. There won¹t be that many symbols, so length should not be an issue and it also preserves the ³P² somehow. We can, of course, change things later Martin On 9/30/15, 6:01 PM, "Bland, Wesley" <wesley.bland(a)intel.com> wrote: >I don¹t think that helps with the not sounds like an inside joke thing. > >> On Sep 30, 2015, at 10:59 AM, Dave Goodell (dgoodell) >><dgoodell(a)cisco.com> wrote: >> >> On Sep 30, 2015, at 9:51 AM, Mohror, Kathryn <mohror1(a)llnl.gov> wrote: >>> >>> Or another idea: MPI_I for MPI Interception Interface? Or >>>Introspection Interface? It kind of rolls off the tongue... for me >>>anyway. MP Eye Eye. >> >> Sounds very nautical: "M P Aye Aye" ;-) >> >> -Dave >> >> _______________________________________________ >> mpiwg-tools mailing list >> mpiwg-tools(a)lists.mpi-forum.org >> http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools > >_______________________________________________ >mpiwg-tools mailing list >mpiwg-tools(a)lists.mpi-forum.org >http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools

1 0

Re: [mpiwg-tools] Reading of ticket #484
by Marc-Andre Hermanns 02 Oct '15

02 Oct '15

Hi John, > I'll be on a plane on 10/8, so I won't be able to make the call. Good to know. So let's try to clear everything beforehand. > Here are my comments (I haven't joined the MPI tool github thingy > yet): Once you have a Github account, let me know and I will add you to the respective groups. >> * Martin pointed out that "the" may be ambiguous and proposed to >> use either "all" or "some" to avoid this ambiguity >> o current definition allows only some of the processes to have >> the symbol >> o in general the new wording should not restrict this >> o might this be problematic for debuggers? >> > > I think the intent is: > > * "the" MPI _starter_ process (e.g., mpiexec, orterun, srun, aprun, > etc.), if there is one. MPICH1 doesn't have a separate starter > process and TotalView still supports it, but I doubt there are any > MPICH1 users anymore. > * "all" MPI processes at the time the MPIR_DEBUG_SPAWNED event is > raised. > > Here's why... If not all MPI processes define the symbol within the > same image file (executable or shared library), it could be > problematic for the debugger. TotalView does not currently set > MPIR_being_debugged in the MPI processes (so this will have to > change), but it does set MPIR_debug_gate in all MPI processes that > define it. For the debug gate variable the TotalView client will > lookup the symbol in a representative process from each unique > executable in the program (the "share group"), and broadcast a write > request with a "segment plus offset" relocatable address for each > share group. The TotalView servers attempt to relocate that address in > each MPI process, but if the process does not load the segment > containing the variable the server skips it. > > So, the problem I can imagine here has to do with the variable being > defined in a shared library and not all processes having the library > loaded at the time the MPIR_DEBUG_SPAWNED event is raised. Also, if > the library defining the symbol is loaded later, the debugger might > not catch that event and set the variable. So do I read this correctly that we actually have to be more restrictive/clearer in the text: If any MPI process defines it, it should be defined in the same shared library and should be available with MPIR_debug_gate. Would this cover your concerns? >> * We need to specify that we set value to 1/0 in the process to >> which we attach/from which we detach >> * Do we allow only 0 and 1 or zero and non-zero values? > > TotalView uses 0 and 1. It seems to me that other non-zero values > might be a problem for the MPI implementation. Ok. >> * Do we need to be more specific on when the debugger sets the >> value back to 0? > > I think we said that it is set to 0 before detaching from the MPI > process. Is that not specific enough? If we are going to kill the job, > there should be no need to set the variable to 0. The question to this arose that "before detach" may also cover longer time spans than "right before detach". Maybe the concern was that it sets it back to 0 and continues access debug information before detaching and this to cause problems. >> * We are unspecific about what happens to the value between attach >> and detach. Do we need to be clearer? > > I think that the MPI implementation is allowed to test the value. I > guess I don't see why it can't also modify it's value if it suits its > purposes. In the text we currently only allow reading for the MPI implementation. At least that is how I interpret the text. The question probably intended to clarify: Is the debugger allowed to change the value at other points that attachment and detachment? An MPI implementation is also allowed to ignore the variable, right? So setting this variable does not guarantee anything to the debugger? Cheers, Marc-Andre -- Marc-Andre Hermanns Jülich Aachen Research Alliance, High Performance Computing (JARA-HPC) Jülich Supercomputing Centre (JSC) Schinkelstrasse 2 52062 Aachen Germany Phone: +49 2461 61 2509 | +49 241 80 24897 Fax: +49 2461 80 6 99753 www.jara.org/jara-hpc email: hermanns(a)jara.rwth-aachen.de

1 0

Re: [mpiwg-tools] Reading of ticket #484
by John DelSignore 01 Oct '15

01 Oct '15

1 0