On Wed, Dec 13, 2017 at 4:07 AM, Nair, Reena via iovisor-dev < iovisor-dev@lists.iovisor.org> wrote:
> Hi, > > I have a tracepoint probe for sched_switch event. While tracing the > context-switches of a multi-threaded program, I would like to get stack > trace of other active threads under certain conditions. > You cannot get stack trace on other threads (tasks) in bpf programs. However, depending on what your "certain conditions" are, you may be able to attach multiple bpf programs to your application, and record stacks with timestamp/taskid etc and coordinate through shared maps, you may post process to find how different tasks progress in the time line. > > Reena > > > > ------------------------------ > *From:* iovisor-dev-boun...@lists.iovisor.org <iovisor-dev-bounces@lists. > iovisor.org> on behalf of iovisor-dev-requ...@lists.iovisor.org < > iovisor-dev-requ...@lists.iovisor.org> > *Sent:* 13 December 2017 12:00 > *To:* iovisor-dev@lists.iovisor.org > *Subject:* iovisor-dev Digest, Vol 28, Issue 1 > > Send iovisor-dev mailing list submissions to > iovisor-dev@lists.iovisor.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.iovisor.org/mailman/listinfo/iovisor-dev > or, via email, send a message with subject or body 'help' to > iovisor-dev-requ...@lists.iovisor.org > > You can reach the person managing the list at > iovisor-dev-ow...@lists.iovisor.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of iovisor-dev digest..." > > > Today's Topics: > > 1. Getting stack trace from a different CPU core (Nair, Reena) > 2. Re: Getting stack trace from a different CPU core (Y Song) > 3. reminder: IO Visor TSC/Dev Meeting (Brenden Blanco) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Dec 2017 14:26:51 +0000 > From: "Nair, Reena" <r.nai...@imperial.ac.uk> > To: "iovisor-dev@lists.iovisor.org" <iovisor-dev@lists.iovisor.org> > Subject: [iovisor-dev] Getting stack trace from a different CPU core > Message-ID: > <AM3PR06MB136450D6EA93C9F2B7C725F9AE340@AM3PR06MB1364. > eurprd06.prod.outlook.com> > > Content-Type: text/plain; charset="iso-8859-1" > > Hello, > > > Is it possible to get stack trace from a different CPU core with eBPF? > > > Thank you, > > Reena > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.iovisor.org/pipermail/iovisor-dev/ > attachments/20171212/01519d06/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Tue, 12 Dec 2017 09:12:09 -0800 > From: Y Song <ys114...@gmail.com> > To: "Nair, Reena" <r.nai...@imperial.ac.uk> > Cc: "iovisor-dev@lists.iovisor.org" <iovisor-dev@lists.iovisor.org> > Subject: Re: [iovisor-dev] Getting stack trace from a different CPU > core > Message-ID: > <CAH3MdRUwePgNrhZmtKn1iWvW2ZjOQCfYDnQrvkfMDkeQtqO6dw@mail. > gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Could you describe your use case? Getting stack trace from a different > CPU involves an > IPI (inter-processor interrupt) which is beyond bpf. But typically you > could run your programs > on both cpus and coordinate through maps to dump stack trace only > under certain conditions. > > On Tue, Dec 12, 2017 at 6:26 AM, Nair, Reena via iovisor-dev > <iovisor-dev@lists.iovisor.org> wrote: > > Hello, > > > > > > Is it possible to get stack trace from a different CPU core with eBPF? > > > > > > Thank you, > > > > Reena > > > > > > _______________________________________________ > > iovisor-dev mailing list > > iovisor-dev@lists.iovisor.org > > https://lists.iovisor.org/mailman/listinfo/iovisor-dev > > > > > ------------------------------ > > Message: 3 > Date: Tue, 12 Dec 2017 16:46:32 -0800 > From: Brenden Blanco <bbla...@gmail.com> > To: iovisor-dev <iovisor-dev@lists.iovisor.org> > Subject: [iovisor-dev] reminder: IO Visor TSC/Dev Meeting > Message-ID: > <CAH9hs-K6zTijO6uQLo5d5MD+=qrWZ=NaxXDtx2xC9WuxghW29g@ > mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Please join us tomorrow for our bi-weekly call. As usual, this meeting is > open to everybody and completely optional. > You might be interested to join if: > You want to know what is going on in BPF land > You are doing something interesting yourself with BPF and would like to > share > You want to know what the heck BPF is > > === IO Visor Dev/TSC Meeting === > > Every 2 weeks on Wednesday, from Wednesday, January 25, 2017, to no end > date > 11:00 am | Pacific Daylight Time (San Francisco, GMT-08:00) | 30 min > > https://bluejeans.com/568677804/ > BlueJeans Network | Video Collaboration in the Cloud > <https://bluejeans.com/568677804/> > bluejeans.com > BlueJeans Network - Interoperable, Cloud-based, Affordable Video > Conferencing Service > > > https://www.timeanddate.com/worldclock/meetingdetails. > html?year=2017&month=12&day=13&hour=19&min=0&sec=0&p1=900 > > <https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=12&day=13&hour=19&min=0&sec=0&p1=900> > The World Clock Meeting Planner - Details > <https://www.timeanddate.com/worldclock/meetingdetails.html?year=2017&month=12&day=13&hour=19&min=0&sec=0&p1=900> > www.timeanddate.com > Local time for a meeting, in user selected locations. > > > > ------------------------------ > > _______________________________________________ > iovisor-dev mailing list > iovisor-dev@lists.iovisor.org > https://lists.iovisor.org/mailman/listinfo/iovisor-dev > iovisor-dev Info Page > <https://lists.iovisor.org/mailman/listinfo/iovisor-dev> > lists.iovisor.org > Discussion list for IOVisor development. To see the collection of prior > postings to the list, visit the iovisor-dev Archives. Using iovisor-dev > > > > End of iovisor-dev Digest, Vol 28, Issue 1 > ****************************************** > > _______________________________________________ > iovisor-dev mailing list > iovisor-dev@lists.iovisor.org > https://lists.iovisor.org/mailman/listinfo/iovisor-dev > >
_______________________________________________ iovisor-dev mailing list iovisor-dev@lists.iovisor.org https://lists.iovisor.org/mailman/listinfo/iovisor-dev
