On Tue, May 01, 2018 at 11:43:32AM -0400, Alexander Aring wrote:
...
> >
> > Normally, a trace has a unique UUID. If you cannot ensure this, I
> > suggest that you remove the UUID field from the packet header.
> >
>
> I see, according [0]:
>
> Trace UUID, used to ensure the event packet match
Hi,
On Tue, May 01, 2018 at 11:22:18AM -0400, Philippe Proulx wrote:
...
> >
> > I also thought about: using barectf and generate a object file linked
> > to my platform who has the metadata file inside and will be created to
> > my stream file when barectf init's (if it's not already exists).
>
On Tue, May 1, 2018 at 11:12 AM, Alexander Aring wrote:
> Hi,
>
> On Mon, Apr 30, 2018 at 06:36:08PM -0400, Philippe Proulx wrote:
>> On Mon, Apr 30, 2018 at 5:31 PM, Alexander Aring wrote:
>> >
>> > This patch adds an argument for the fs-src plugin to
Hi,
On Mon, Apr 30, 2018 at 06:36:08PM -0400, Philippe Proulx wrote:
> On Mon, Apr 30, 2018 at 5:31 PM, Alexander Aring wrote:
> >
> > This patch adds an argument for the fs-src plugin to declare the
> > directory to find the metadata file instead of placing it in every
> >
On Mon, Apr 30, 2018 at 6:36 PM, Philippe Proulx
wrote:
> On Mon, Apr 30, 2018 at 5:31 PM, Alexander Aring wrote:
>>
>> This patch adds an argument for the fs-src plugin to declare the
>> directory to find the metadata file instead of placing it in
On Mon, Apr 30, 2018 at 5:31 PM, Alexander Aring wrote:
>
> This patch adds an argument for the fs-src plugin to declare the
> directory to find the metadata file instead of placing it in every
> subdir of traces.
>
> If parameter assign every subdirectory which does not have