July 2017 - mpiwg-tools - mailman3.cels.anl.gov

Re: [mpiwg-tools] Intel MPI Backend Breakpoint
by Jeff Squyres (jsquyres) 13 Jul '17

13 Jul '17

FWIW, we just decided this week in Open MPI to deprecate the MPIR interface in favor of PMIx. > On Jul 12, 2017, at 2:02 PM, Durnov, Dmitry <dmitry.durnov(a)intel.com> wrote: > > Sure. > > Thanks. > > BR, > Dmitry > > -----Original Message----- > From: mpiwg-tools [mailto:[email protected]] On Behalf Of John DelSignore > Sent: Wednesday, July 12, 2017 9:52 PM > To: mpiwg-tools(a)lists.mpi-forum.org > Subject: Re: [mpiwg-tools] Intel MPI Backend Breakpoint > > I'd be interested in being included in that discussion. FWIW, I work on the TotalView debugger and wrote-up the MPIR specification. > > Cheers, John D. > > -----Original Message----- > From: mpiwg-tools [mailto:[email protected]] On Behalf Of Durnov, Dmitry > Sent: Wednesday, July 12, 2017 2:44 PM > To: mpiwg-tools(a)lists.mpi-forum.org > Subject: Re: [mpiwg-tools] Intel MPI Backend Breakpoint > > Hi Alex, > > I've started a separate mail thread where we may discuss details. > > Thanks. > > BR, > Dmitry > > -----Original Message----- > From: mpiwg-tools [mailto:[email protected]] On Behalf Of Alexander Zahdeh > Sent: Wednesday, July 12, 2017 7:27 PM > To: mpiwg-tools(a)lists.mpi-forum.org > Subject: [mpiwg-tools] Intel MPI Backend Breakpoint > > Hi, > > This is Alex Zahdeh, one of the debugger tools developers at Cray. I had a question about how Intel MPI handles synchronization according to the MPIR debugging standard. The usual procedure for our debugger is to launch tool daemons to attach to the backend application processes while the application launcher is held at MPIR_Breakpoint. At this point the application process must be in some sort of barrier so the debugger tries to return the user to their own code by setting breakpoints at various initialization symbols for different parallel models, continuing, hitting one of the breakpoints, deleting the rest and finishing the current function. This works if the application is held before the breakpoints we set which does not seem to be the case with Intel MPI. Is there a more standard approach to returning the user to their own code or does it vary by programming model and implementor? And specifically with Intel MPI would there be a good breakpoint to set in this scenario? > > Thanks much, > Alex > -- > Alex Zahdeh | PE Debugger Development | Cray Inc. > azahdeh(a)cray.com | Office: 651-967-9628 | Cell: 651-300-2005 _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools > > -------------------------------------------------------------------- > Joint Stock Company Intel A/O > Registered legal address: Krylatsky Hills Business Park, > 17 Krylatskaya Str., Bldg 4, Moscow 121614, Russian Federation > > This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools > > -------------------------------------------------------------------- > Joint Stock Company Intel A/O > Registered legal address: Krylatsky Hills Business Park, > 17 Krylatskaya Str., Bldg 4, Moscow 121614, > Russian Federation > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > > _______________________________________________ > mpiwg-tools mailing list > mpiwg-tools(a)lists.mpi-forum.org > https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools -- Jeff Squyres jsquyres(a)cisco.com

1 0

Meeting tomorrow
by Mohror, Kathryn 12 Jul '17

12 Jul '17

Hi all, It's been a really long time since we held the alternate week meeting for tools, so it's high time to start it back up again. For the time being, we're going to back away from talking about debugger start up and move to other issues, e.g. timers in MPIT, the interaction of tools and MPI Sessions, etc. Tomorrow, lets plan on discussing the list of topics that need work and figure out priorities. Talk to you soon! --- Kathryn Sent from my phone

1 0

Re: [mpiwg-tools] Intel MPI Backend Breakpoint
by Durnov, Dmitry 12 Jul '17

12 Jul '17

Sure. Thanks. BR, Dmitry -----Original Message----- From: mpiwg-tools [mailto:[email protected]] On Behalf Of John DelSignore Sent: Wednesday, July 12, 2017 9:52 PM To: mpiwg-tools(a)lists.mpi-forum.org Subject: Re: [mpiwg-tools] Intel MPI Backend Breakpoint I'd be interested in being included in that discussion. FWIW, I work on the TotalView debugger and wrote-up the MPIR specification. Cheers, John D. -----Original Message----- From: mpiwg-tools [mailto:[email protected]] On Behalf Of Durnov, Dmitry Sent: Wednesday, July 12, 2017 2:44 PM To: mpiwg-tools(a)lists.mpi-forum.org Subject: Re: [mpiwg-tools] Intel MPI Backend Breakpoint Hi Alex, I've started a separate mail thread where we may discuss details. Thanks. BR, Dmitry -----Original Message----- From: mpiwg-tools [mailto:[email protected]] On Behalf Of Alexander Zahdeh Sent: Wednesday, July 12, 2017 7:27 PM To: mpiwg-tools(a)lists.mpi-forum.org Subject: [mpiwg-tools] Intel MPI Backend Breakpoint Hi, This is Alex Zahdeh, one of the debugger tools developers at Cray. I had a question about how Intel MPI handles synchronization according to the MPIR debugging standard. The usual procedure for our debugger is to launch tool daemons to attach to the backend application processes while the application launcher is held at MPIR_Breakpoint. At this point the application process must be in some sort of barrier so the debugger tries to return the user to their own code by setting breakpoints at various initialization symbols for different parallel models, continuing, hitting one of the breakpoints, deleting the rest and finishing the current function. This works if the application is held before the breakpoints we set which does not seem to be the case with Intel MPI. Is there a more standard approach to returning the user to their own code or does it vary by programming model and implementor? And specifically with Intel MPI would there be a good breakpoint to set in this scenario? Thanks much, Alex -- Alex Zahdeh | PE Debugger Development | Cray Inc. azahdeh(a)cray.com | Office: 651-967-9628 | Cell: 651-300-2005 _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools -------------------------------------------------------------------- Joint Stock Company Intel A/O Registered legal address: Krylatsky Hills Business Park, 17 Krylatskaya Str., Bldg 4, Moscow 121614, Russian Federation This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools -------------------------------------------------------------------- Joint Stock Company Intel A/O Registered legal address: Krylatsky Hills Business Park, 17 Krylatskaya Str., Bldg 4, Moscow 121614, Russian Federation This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

Re: [mpiwg-tools] Intel MPI Backend Breakpoint
by John DelSignore 12 Jul '17

12 Jul '17

I'd be interested in being included in that discussion. FWIW, I work on the TotalView debugger and wrote-up the MPIR specification. Cheers, John D. -----Original Message----- From: mpiwg-tools [mailto:[email protected]] On Behalf Of Durnov, Dmitry Sent: Wednesday, July 12, 2017 2:44 PM To: mpiwg-tools(a)lists.mpi-forum.org Subject: Re: [mpiwg-tools] Intel MPI Backend Breakpoint Hi Alex, I've started a separate mail thread where we may discuss details. Thanks. BR, Dmitry -----Original Message----- From: mpiwg-tools [mailto:[email protected]] On Behalf Of Alexander Zahdeh Sent: Wednesday, July 12, 2017 7:27 PM To: mpiwg-tools(a)lists.mpi-forum.org Subject: [mpiwg-tools] Intel MPI Backend Breakpoint Hi, This is Alex Zahdeh, one of the debugger tools developers at Cray. I had a question about how Intel MPI handles synchronization according to the MPIR debugging standard. The usual procedure for our debugger is to launch tool daemons to attach to the backend application processes while the application launcher is held at MPIR_Breakpoint. At this point the application process must be in some sort of barrier so the debugger tries to return the user to their own code by setting breakpoints at various initialization symbols for different parallel models, continuing, hitting one of the breakpoints, deleting the rest and finishing the current function. This works if the application is held before the breakpoints we set which does not seem to be the case with Intel MPI. Is there a more standard approach to returning the user to their own code or does it vary by programming model and implementor? And specifically with Intel MPI would there be a good breakpoint to set in this scenario? Thanks much, Alex -- Alex Zahdeh | PE Debugger Development | Cray Inc. azahdeh(a)cray.com | Office: 651-967-9628 | Cell: 651-300-2005 _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools -------------------------------------------------------------------- Joint Stock Company Intel A/O Registered legal address: Krylatsky Hills Business Park, 17 Krylatskaya Str., Bldg 4, Moscow 121614, Russian Federation This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools

1 0

Re: [mpiwg-tools] Intel MPI Backend Breakpoint
by Durnov, Dmitry 12 Jul '17

12 Jul '17

Hi Alex, I've started a separate mail thread where we may discuss details. Thanks. BR, Dmitry -----Original Message----- From: mpiwg-tools [mailto:[email protected]] On Behalf Of Alexander Zahdeh Sent: Wednesday, July 12, 2017 7:27 PM To: mpiwg-tools(a)lists.mpi-forum.org Subject: [mpiwg-tools] Intel MPI Backend Breakpoint Hi, This is Alex Zahdeh, one of the debugger tools developers at Cray. I had a question about how Intel MPI handles synchronization according to the MPIR debugging standard. The usual procedure for our debugger is to launch tool daemons to attach to the backend application processes while the application launcher is held at MPIR_Breakpoint. At this point the application process must be in some sort of barrier so the debugger tries to return the user to their own code by setting breakpoints at various initialization symbols for different parallel models, continuing, hitting one of the breakpoints, deleting the rest and finishing the current function. This works if the application is held before the breakpoints we set which does not seem to be the case with Intel MPI. Is there a more standard approach to returning the user to their own code or does it vary by programming model and implementor? And specifically with Intel MPI would there be a good breakpoint to set in this scenario? Thanks much, Alex -- Alex Zahdeh | PE Debugger Development | Cray Inc. azahdeh(a)cray.com | Office: 651-967-9628 | Cell: 651-300-2005 _______________________________________________ mpiwg-tools mailing list mpiwg-tools(a)lists.mpi-forum.org https://lists.mpi-forum.org/mailman/listinfo/mpiwg-tools -------------------------------------------------------------------- Joint Stock Company Intel A/O Registered legal address: Krylatsky Hills Business Park, 17 Krylatskaya Str., Bldg 4, Moscow 121614, Russian Federation This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

Intel MPI Backend Breakpoint
by Alexander Zahdeh 12 Jul '17

12 Jul '17

Hi, This is Alex Zahdeh, one of the debugger tools developers at Cray. I had a question about how Intel MPI handles synchronization according to the MPIR debugging standard. The usual procedure for our debugger is to launch tool daemons to attach to the backend application processes while the application launcher is held at MPIR_Breakpoint. At this point the application process must be in some sort of barrier so the debugger tries to return the user to their own code by setting breakpoints at various initialization symbols for different parallel models, continuing, hitting one of the breakpoints, deleting the rest and finishing the current function. This works if the application is held before the breakpoints we set which does not seem to be the case with Intel MPI. Is there a more standard approach to returning the user to their own code or does it vary by programming model and implementor? And specifically with Intel MPI would there be a good breakpoint to set in this scenario? Thanks much, Alex -- Alex Zahdeh | PE Debugger Development | Cray Inc. azahdeh(a)cray.com | Office: 651-967-9628 | Cell: 651-300-2005

1 0

Re: [mpiwg-tools] Reminder for call: Today Jul 6, 2017 on performance tools
by Marc-Andre Hermanns 06 Jul '17

06 Jul '17

Dear all, my bus home accumulated some delay, so I will join the call a couple minutes late. Sorry for that. Cheers, Marc-Andre Am 6. Juli 2017 15:43:14 MESZ schrieb Marc-Andre Hermanns <hermanns(a)jara.rwth-aachen.de>: >Dear all, > >this is a friendly reminder that we have our call on performance tools. > >Agenda: >- Recap of face to face meeting >- New PR for ticket #6 >- Event dependencies within MPI_T events. > >Cheers >Marc-Andre --

1 0

Reminder for call: Today Jul 6, 2017 on performance tools
by Marc-Andre Hermanns 06 Jul '17

06 Jul '17

Dear all, this is a friendly reminder that we have our call on performance tools. Agenda: - Recap of face to face meeting - New PR for ticket #6 - Event dependencies within MPI_T events. Cheers Marc-Andre -- Sent from phone - type no good.

1 0