Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Paul_Woegerer@mentor.com (Woegerer, Paul)
Subject: [lttng-dev] Machine Interface
Date: Thu, 6 Feb 2014 08:41:46 +0100	[thread overview]
Message-ID: <52F33CBA.5000802@mentor.com> (raw)
In-Reply-To: <20140206024218.GD23121@gmail.com>

On 02/06/2014 03:42 AM, Jonathan Rajotte wrote:
> Hello all,
>
> After speaking with Michel Dagenais, Genevi?ve Bastien, folks over at EfficiOs
> and Ericsson, a machine interface for lttng-tool would be a nice feature
> to have. Olivier Cotte and me will be working on MI for the
> next few weeks.
>
> The main objective would be to reduce parsing complexity
> in control tools.
> ex:Regex used in TMF control service.
> (org.eclipse.linuxtools.internal.lttng2.ui.views.control.service.LTTngControlService.java)
>
> Multiples solutions come to mind:
> -XML
> -JSON
> -YAML

YAML sounds very attractive in this context.

It's easily parseable even from a shell script. If you need to automate
LTTng tracing tasks on a small embedded target busybox is all you have!

Best,
Paul

> -Custom syntax (like GDB Machine interface* as proposed by Alexandre
> 				Montplaisir)
>
> XML/JSON/YAML promote extensibility and ease of development for new tools
> dependant on lttng-tools by being established standards.
> On the other hand, they add dependencies to lttng-tools where a custom syntax
> would not.
>
> Machine interface output would be generated only with --mi option and
> could contain additional information than regular output.
>
> We are focusing on output right now but we may eventually add a 'mi'
> command for input if necessary.
>
> What do you think ?
>
> Thanks
>
>
> *https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI.html
>


-- 
Paul Woegerer, SW Development Engineer
Sourcery Analyzer <http://go.mentor.com/sourceryanalyzer>
Mentor Graphics, Embedded Software Division




  reply	other threads:[~2014-02-06  7:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06  2:42 Jonathan Rajotte
2014-02-06  7:41 ` Woegerer, Paul [this message]
2014-02-06 13:32   ` Simon Marchi
2014-02-06 17:07     ` Woegerer, Paul
2014-02-06 18:40       ` Simon Marchi
2014-02-06 16:11 ` Christian Babeux
2014-02-06 17:00   ` Jonathan Rajotte
2014-02-06 18:21     ` Christian Babeux
2014-02-06 13:51 Thibault, Daniel
2014-02-13 18:00 Olivier Cotte
2014-02-13 18:26 ` Simon Marchi
2014-02-13 19:16   ` Jonathan Rajotte
2014-02-13 20:05 Thibault, Daniel
2014-02-13 20:36 ` Jonathan Rajotte
2014-02-13 20:41   ` Thibault, Daniel

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=52F33CBA.5000802@mentor.com \
    --to=paul_woegerer@mentor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox