All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Desfossez <jdesfossez@efficios.com>
To: diamon-discuss@lists.linuxfoundation.org
Cc: Joel Fernandes <joelaf@google.com>,
	Fabien Sanglard <sanglardf@google.com>
Subject: Re: [diamon-discuss] Next meeting: Android Tracing, Friday December 2nd, 1PM EST (6PM UTC)
Date: Wed, 23 Nov 2016 15:08:28 -0500	[thread overview]
Message-ID: <0a9051a1-8365-95e2-b816-51dc6c4d4f08@efficios.com> (raw)
In-Reply-To: <ed30f4d8-c482-d129-cc77-e3221fff6de7@efficios.com>

On 2016-11-23 12:28 PM, Julien Desfossez wrote:
> Hi,
> 
> The next Diamon meeting will be presented by Joel Fernandes and Fabien
> Sanglard from Google, and it will be about Android tracing.
> 
> Abstract:
> "systrace is the defacto android tool currently used to trace and
> monitor android applications, kernel and system behavior. It is based
> on ftrace events and trace markers. This talk is a brief introduction
> to systrace features, some usecases for tracing that are required
> along with systrace screenshots and discuss some of the challenges
> other tools may face with integrating with Android."
> 
> Details to join the conference:
> https://www.uberconference.com/diamon
> Phone: 716-293-7271
> Pin: 37262

Also, here is the list of international phone numbers:
https://www.uberconference.com/international

Julien

  reply	other threads:[~2016-11-23 20:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-23 17:28 [diamon-discuss] Next meeting: Android Tracing, Friday December 2nd, 1PM EST (6PM UTC) Julien Desfossez
2016-11-23 20:08 ` Julien Desfossez [this message]
2016-12-01 17:29   ` Julien Desfossez
2016-12-01 21:32     ` Joel Fernandes
2016-12-01 21:39       ` Julien Desfossez
2016-12-02  1:51         ` Joel Fernandes
2016-12-02  3:28           ` Fabien Sanglard
2016-12-02 19:44             ` Julien Desfossez
2016-12-02 20:54               ` Joel Fernandes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0a9051a1-8365-95e2-b816-51dc6c4d4f08@efficios.com \
    --to=jdesfossez@efficios.com \
    --cc=diamon-discuss@lists.linuxfoundation.org \
    --cc=joelaf@google.com \
    --cc=sanglardf@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.