Reland of tracing v2: Introduce TraceBufferWriter (https://codereview.chromium.org/2196663002)

Reland of tracing v2: Introduce TraceBufferWriter (https://codereview.chromium.org/2196663002)

Reason for reland:
fixing undefined behavior of move constructor which failed on windows.

Original issue's description:
> tracing v2: Introduce TraceBufferWriter
>
> TraceBufferWriter is the main building block that allows writing
> events into the trace ring buffer. TBW is responsible of exchanging
> chunks with the ring buffer and carving out events out of them.
> The expected design is 1 TraceBufferWriter per thread (% very special
> cases like worker pools which don't have a message loop).
> The major challenge is represented by the fact that events can spread
> over several chunks. TBW is responsible of owning chunks for the
> all lifetime of the event, and returning them as soon as the event
> is finalized.
> In the next CLs:
>  - This code will be properly integrated with the stubs generated by
>    the protozero protoc compiler plugin.
>  - The actual event.proto will be introduced, and TBW::AddEvent will
>    return a more structured object other than just a ProtoZeroMessage.
>
> BUG=608719
> TEST=TraceBufferWriterTest.*
>
> Committed: https://crrev.com/9cc78e4aea540c6eba8655d8557b068bde423152
> Cr-Commit-Position: refs/heads/master@{#410669}

TBR=alph@chromium.org,oysteine@chromium.org,kraynov@chromium.org
BUG=608719
Committed: https://crrev.com/494ffeb22edae2db58c5ff88093442246a64e087
Cr-Commit-Position: refs/heads/master@{#414063}

[Primiano Tucci (use gerrit), 2016-08-24 08:37:06]

The CQ bit was checked by primiano@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-08-24 08:37:31]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[Primiano Tucci (use gerrit), 2016-08-24 08:38:39]

Description was changed from

==========
Reland of tracing v2: Introduce TraceBufferWriter
(https://codereview.chromium.org/2196663002)

Reason for reland:
fixing undefined behavior of move constructor which failed on windows.

Original issue's description:
> tracing v2: Introduce TraceBufferWriter
>
> TraceBufferWriter is the main building block that allows writing
> events into the trace ring buffer. TBW is responsible of exchanging
> chunks with the ring buffer and carving out events out of them.
> The expected design is 1 TraceBufferWriter per thread (% very special
> cases like worker pools which don't have a message loop).
> The major challenge is represented by the fact that events can spread
> over several chunks. TBW is responsible of owning chunks for the
> all lifetime of the event, and returning them as soon as the event
> is finalized.
> In the next CLs:
>  - This code will be properly integrated with the stubs generated by
>    the protozero protoc compiler plugin.
>  - The actual event.proto will be introduced, and TBW::AddEvent will
>    return a more structured object other than just a ProtoZeroMessage.
>
> BUG=608719
> TEST=TraceBufferWriterTest.*
>
> Committed: https://crrev.com/9cc78e4aea540c6eba8655d8557b068bde423152
> Cr-Commit-Position: refs/heads/master@{#410669}

TBR=alph@chromium.org,oysteine@chromium.org
BUG=608719
==========

to

==========
Reland of tracing v2: Introduce TraceBufferWriter
(https://codereview.chromium.org/2196663002)

Reason for reland:
fixing undefined behavior of move constructor which failed on windows.

Original issue's description:
> tracing v2: Introduce TraceBufferWriter
>
> TraceBufferWriter is the main building block that allows writing
> events into the trace ring buffer. TBW is responsible of exchanging
> chunks with the ring buffer and carving out events out of them.
> The expected design is 1 TraceBufferWriter per thread (% very special
> cases like worker pools which don't have a message loop).
> The major challenge is represented by the fact that events can spread
> over several chunks. TBW is responsible of owning chunks for the
> all lifetime of the event, and returning them as soon as the event
> is finalized.
> In the next CLs:
>  - This code will be properly integrated with the stubs generated by
>    the protozero protoc compiler plugin.
>  - The actual event.proto will be introduced, and TBW::AddEvent will
>    return a more structured object other than just a ProtoZeroMessage.
>
> BUG=608719
> TEST=TraceBufferWriterTest.*
>
> Committed: https://crrev.com/9cc78e4aea540c6eba8655d8557b068bde423152
> Cr-Commit-Position: refs/heads/master@{#410669}

TBR=alph@chromium.org,oysteine@chromium.org,kraynov@chromium.org
BUG=608719
==========

[commit-bot: I haz the power, 2016-08-24 10:38:15]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-08-24 10:38:16]

Dry run: Try jobs failed on following builders:
  linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[Primiano Tucci (use gerrit), 2016-08-24 12:33:19]

The CQ bit was checked by primiano@chromium.org

[commit-bot: I haz the power, 2016-08-24 12:33:32]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-08-24 13:44:52]

Description was changed from

==========
Reland of tracing v2: Introduce TraceBufferWriter
(https://codereview.chromium.org/2196663002)

Reason for reland:
fixing undefined behavior of move constructor which failed on windows.

Original issue's description:
> tracing v2: Introduce TraceBufferWriter
>
> TraceBufferWriter is the main building block that allows writing
> events into the trace ring buffer. TBW is responsible of exchanging
> chunks with the ring buffer and carving out events out of them.
> The expected design is 1 TraceBufferWriter per thread (% very special
> cases like worker pools which don't have a message loop).
> The major challenge is represented by the fact that events can spread
> over several chunks. TBW is responsible of owning chunks for the
> all lifetime of the event, and returning them as soon as the event
> is finalized.
> In the next CLs:
>  - This code will be properly integrated with the stubs generated by
>    the protozero protoc compiler plugin.
>  - The actual event.proto will be introduced, and TBW::AddEvent will
>    return a more structured object other than just a ProtoZeroMessage.
>
> BUG=608719
> TEST=TraceBufferWriterTest.*
>
> Committed: https://crrev.com/9cc78e4aea540c6eba8655d8557b068bde423152
> Cr-Commit-Position: refs/heads/master@{#410669}

TBR=alph@chromium.org,oysteine@chromium.org,kraynov@chromium.org
BUG=608719
==========

to

==========
Reland of tracing v2: Introduce TraceBufferWriter
(https://codereview.chromium.org/2196663002)

Reason for reland:
fixing undefined behavior of move constructor which failed on windows.

Original issue's description:
> tracing v2: Introduce TraceBufferWriter
>
> TraceBufferWriter is the main building block that allows writing
> events into the trace ring buffer. TBW is responsible of exchanging
> chunks with the ring buffer and carving out events out of them.
> The expected design is 1 TraceBufferWriter per thread (% very special
> cases like worker pools which don't have a message loop).
> The major challenge is represented by the fact that events can spread
> over several chunks. TBW is responsible of owning chunks for the
> all lifetime of the event, and returning them as soon as the event
> is finalized.
> In the next CLs:
>  - This code will be properly integrated with the stubs generated by
>    the protozero protoc compiler plugin.
>  - The actual event.proto will be introduced, and TBW::AddEvent will
>    return a more structured object other than just a ProtoZeroMessage.
>
> BUG=608719
> TEST=TraceBufferWriterTest.*
>
> Committed: https://crrev.com/9cc78e4aea540c6eba8655d8557b068bde423152
> Cr-Commit-Position: refs/heads/master@{#410669}

TBR=alph@chromium.org,oysteine@chromium.org,kraynov@chromium.org
BUG=608719
==========

[commit-bot: I haz the power, 2016-08-24 13:44:53]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2016-08-24 13:46:29]

Description was changed from

==========
Reland of tracing v2: Introduce TraceBufferWriter
(https://codereview.chromium.org/2196663002)

Reason for reland:
fixing undefined behavior of move constructor which failed on windows.

Original issue's description:
> tracing v2: Introduce TraceBufferWriter
>
> TraceBufferWriter is the main building block that allows writing
> events into the trace ring buffer. TBW is responsible of exchanging
> chunks with the ring buffer and carving out events out of them.
> The expected design is 1 TraceBufferWriter per thread (% very special
> cases like worker pools which don't have a message loop).
> The major challenge is represented by the fact that events can spread
> over several chunks. TBW is responsible of owning chunks for the
> all lifetime of the event, and returning them as soon as the event
> is finalized.
> In the next CLs:
>  - This code will be properly integrated with the stubs generated by
>    the protozero protoc compiler plugin.
>  - The actual event.proto will be introduced, and TBW::AddEvent will
>    return a more structured object other than just a ProtoZeroMessage.
>
> BUG=608719
> TEST=TraceBufferWriterTest.*
>
> Committed: https://crrev.com/9cc78e4aea540c6eba8655d8557b068bde423152
> Cr-Commit-Position: refs/heads/master@{#410669}

TBR=alph@chromium.org,oysteine@chromium.org,kraynov@chromium.org
BUG=608719
==========

to

==========
Reland of tracing v2: Introduce TraceBufferWriter
(https://codereview.chromium.org/2196663002)

Reason for reland:
fixing undefined behavior of move constructor which failed on windows.

Original issue's description:
> tracing v2: Introduce TraceBufferWriter
>
> TraceBufferWriter is the main building block that allows writing
> events into the trace ring buffer. TBW is responsible of exchanging
> chunks with the ring buffer and carving out events out of them.
> The expected design is 1 TraceBufferWriter per thread (% very special
> cases like worker pools which don't have a message loop).
> The major challenge is represented by the fact that events can spread
> over several chunks. TBW is responsible of owning chunks for the
> all lifetime of the event, and returning them as soon as the event
> is finalized.
> In the next CLs:
>  - This code will be properly integrated with the stubs generated by
>    the protozero protoc compiler plugin.
>  - The actual event.proto will be introduced, and TBW::AddEvent will
>    return a more structured object other than just a ProtoZeroMessage.
>
> BUG=608719
> TEST=TraceBufferWriterTest.*
>
> Committed: https://crrev.com/9cc78e4aea540c6eba8655d8557b068bde423152
> Cr-Commit-Position: refs/heads/master@{#410669}

TBR=alph@chromium.org,oysteine@chromium.org,kraynov@chromium.org
BUG=608719

Committed: https://crrev.com/494ffeb22edae2db58c5ff88093442246a64e087
Cr-Commit-Position: refs/heads/master@{#414063}
==========

[commit-bot: I haz the power, 2016-08-24 13:46:30]

Patchset 4 (id:??) landed as
https://crrev.com/494ffeb22edae2db58c5ff88093442246a64e087
Cr-Commit-Position: refs/heads/master@{#414063}