[XRay] FDRTraceWriter and FDR Trace Loading
Summary:
This is the first step in the larger refactoring and reduction of
D50441.
This step in the process does the following:
- Introduces more granular types of `Record`s representing the many
kinds of records written/read by the Flight Data Recorder (FDR) mode
`Trace` loading function(s).
- Introduces an abstract `RecordVisitor` type meant to handle the
processing of the various `Record` derived types. This `RecordVisitor`
has two implementations in this patch: `RecordInitializer` and
`FDRTraceWriter`.
- We also introduce a convenience interface for building a collection of
`Record` instances called a `LogBuilder`. This allows us to generate
sequences of `Record` instances manually (used in unit tests but
useful otherwise).
- The`FDRTraceWriter` class implements the `RecordVisitor` interface and
handles the writing of metadata records to a `raw_ostream`. We
demonstrate that in the unit test, we can generate in-memory FDR mode
traces using the specific `Record` derived types, which we load
through the `loadTrace(...)` function yielding valid `Trace` objects.
This patch introduces the required types and concepts for us to start
replacing the logic implemented in the `loadFDRLog` function to use the
more granular types. In subsequent patches, we will introduce more
visitor implementations which isolate the verification, printing,
indexing, production/consumption, and finally the conversion of the FDR
mode logs.
The overarching goal of these changes is to make handling FDR mode logs
better tested, more understandable, more extensible, and more
systematic. This will also allow us to better represent the execution
trace, as we improve the fidelity of the events we represent in an XRay
`Trace` object, which we intend to do after FDR mode log processing is
in better shape.
Reviewers: eizan
Reviewed By: eizan
Subscribers: mgorny, hiraditya, llvm-commits
Differential Revision: https://reviews.llvm.org/D51210
llvm-svn: 341029
2018-08-30 15:22:21 +08:00
|
|
|
//===- FDRTraceWriter.cpp - XRay FDR Trace Writer ---------------*- C++ -*-===//
|
|
|
|
//
|
|
|
|
// The LLVM Compiler Infrastructure
|
|
|
|
//
|
|
|
|
// This file is distributed under the University of Illinois Open Source
|
|
|
|
// License. See LICENSE.TXT for details.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
//
|
|
|
|
// Test a utility that can write out XRay FDR Mode formatted trace files.
|
|
|
|
//
|
|
|
|
//===----------------------------------------------------------------------===//
|
|
|
|
#include "llvm/XRay/FDRTraceWriter.h"
|
|
|
|
#include <tuple>
|
|
|
|
|
|
|
|
namespace llvm {
|
|
|
|
namespace xray {
|
|
|
|
|
|
|
|
namespace {
|
|
|
|
|
|
|
|
struct alignas(32) FileHeader {
|
|
|
|
uint16_t Version;
|
|
|
|
uint16_t Type;
|
2018-08-31 18:03:52 +08:00
|
|
|
uint32_t BitField;
|
|
|
|
uint64_t CycleFrequency;
|
[XRay] FDRTraceWriter and FDR Trace Loading
Summary:
This is the first step in the larger refactoring and reduction of
D50441.
This step in the process does the following:
- Introduces more granular types of `Record`s representing the many
kinds of records written/read by the Flight Data Recorder (FDR) mode
`Trace` loading function(s).
- Introduces an abstract `RecordVisitor` type meant to handle the
processing of the various `Record` derived types. This `RecordVisitor`
has two implementations in this patch: `RecordInitializer` and
`FDRTraceWriter`.
- We also introduce a convenience interface for building a collection of
`Record` instances called a `LogBuilder`. This allows us to generate
sequences of `Record` instances manually (used in unit tests but
useful otherwise).
- The`FDRTraceWriter` class implements the `RecordVisitor` interface and
handles the writing of metadata records to a `raw_ostream`. We
demonstrate that in the unit test, we can generate in-memory FDR mode
traces using the specific `Record` derived types, which we load
through the `loadTrace(...)` function yielding valid `Trace` objects.
This patch introduces the required types and concepts for us to start
replacing the logic implemented in the `loadFDRLog` function to use the
more granular types. In subsequent patches, we will introduce more
visitor implementations which isolate the verification, printing,
indexing, production/consumption, and finally the conversion of the FDR
mode logs.
The overarching goal of these changes is to make handling FDR mode logs
better tested, more understandable, more extensible, and more
systematic. This will also allow us to better represent the execution
trace, as we improve the fidelity of the events we represent in an XRay
`Trace` object, which we intend to do after FDR mode log processing is
in better shape.
Reviewers: eizan
Reviewed By: eizan
Subscribers: mgorny, hiraditya, llvm-commits
Differential Revision: https://reviews.llvm.org/D51210
llvm-svn: 341029
2018-08-30 15:22:21 +08:00
|
|
|
char FreeForm[16];
|
|
|
|
};
|
|
|
|
|
|
|
|
struct MetadataBlob {
|
|
|
|
uint8_t Type : 1;
|
|
|
|
uint8_t RecordKind : 7;
|
|
|
|
char Data[15];
|
2018-08-30 15:57:32 +08:00
|
|
|
};
|
[XRay] FDRTraceWriter and FDR Trace Loading
Summary:
This is the first step in the larger refactoring and reduction of
D50441.
This step in the process does the following:
- Introduces more granular types of `Record`s representing the many
kinds of records written/read by the Flight Data Recorder (FDR) mode
`Trace` loading function(s).
- Introduces an abstract `RecordVisitor` type meant to handle the
processing of the various `Record` derived types. This `RecordVisitor`
has two implementations in this patch: `RecordInitializer` and
`FDRTraceWriter`.
- We also introduce a convenience interface for building a collection of
`Record` instances called a `LogBuilder`. This allows us to generate
sequences of `Record` instances manually (used in unit tests but
useful otherwise).
- The`FDRTraceWriter` class implements the `RecordVisitor` interface and
handles the writing of metadata records to a `raw_ostream`. We
demonstrate that in the unit test, we can generate in-memory FDR mode
traces using the specific `Record` derived types, which we load
through the `loadTrace(...)` function yielding valid `Trace` objects.
This patch introduces the required types and concepts for us to start
replacing the logic implemented in the `loadFDRLog` function to use the
more granular types. In subsequent patches, we will introduce more
visitor implementations which isolate the verification, printing,
indexing, production/consumption, and finally the conversion of the FDR
mode logs.
The overarching goal of these changes is to make handling FDR mode logs
better tested, more understandable, more extensible, and more
systematic. This will also allow us to better represent the execution
trace, as we improve the fidelity of the events we represent in an XRay
`Trace` object, which we intend to do after FDR mode log processing is
in better shape.
Reviewers: eizan
Reviewed By: eizan
Subscribers: mgorny, hiraditya, llvm-commits
Differential Revision: https://reviews.llvm.org/D51210
llvm-svn: 341029
2018-08-30 15:22:21 +08:00
|
|
|
|
|
|
|
struct FunctionDeltaBlob {
|
|
|
|
uint8_t Type : 1;
|
|
|
|
uint8_t RecordKind : 3;
|
|
|
|
int FuncId : 28;
|
|
|
|
uint32_t TSCDelta;
|
2018-08-30 15:57:32 +08:00
|
|
|
};
|
[XRay] FDRTraceWriter and FDR Trace Loading
Summary:
This is the first step in the larger refactoring and reduction of
D50441.
This step in the process does the following:
- Introduces more granular types of `Record`s representing the many
kinds of records written/read by the Flight Data Recorder (FDR) mode
`Trace` loading function(s).
- Introduces an abstract `RecordVisitor` type meant to handle the
processing of the various `Record` derived types. This `RecordVisitor`
has two implementations in this patch: `RecordInitializer` and
`FDRTraceWriter`.
- We also introduce a convenience interface for building a collection of
`Record` instances called a `LogBuilder`. This allows us to generate
sequences of `Record` instances manually (used in unit tests but
useful otherwise).
- The`FDRTraceWriter` class implements the `RecordVisitor` interface and
handles the writing of metadata records to a `raw_ostream`. We
demonstrate that in the unit test, we can generate in-memory FDR mode
traces using the specific `Record` derived types, which we load
through the `loadTrace(...)` function yielding valid `Trace` objects.
This patch introduces the required types and concepts for us to start
replacing the logic implemented in the `loadFDRLog` function to use the
more granular types. In subsequent patches, we will introduce more
visitor implementations which isolate the verification, printing,
indexing, production/consumption, and finally the conversion of the FDR
mode logs.
The overarching goal of these changes is to make handling FDR mode logs
better tested, more understandable, more extensible, and more
systematic. This will also allow us to better represent the execution
trace, as we improve the fidelity of the events we represent in an XRay
`Trace` object, which we intend to do after FDR mode log processing is
in better shape.
Reviewers: eizan
Reviewed By: eizan
Subscribers: mgorny, hiraditya, llvm-commits
Differential Revision: https://reviews.llvm.org/D51210
llvm-svn: 341029
2018-08-30 15:22:21 +08:00
|
|
|
|
|
|
|
template <size_t Index> struct IndexedMemcpy {
|
|
|
|
template <
|
|
|
|
class Tuple,
|
|
|
|
typename std::enable_if<
|
|
|
|
(Index <
|
|
|
|
std::tuple_size<typename std::remove_reference<Tuple>::type>::value),
|
|
|
|
int>::type = 0>
|
|
|
|
static void Copy(char *Dest, Tuple &&T) {
|
|
|
|
auto Next = static_cast<char *>(std::memcpy(
|
|
|
|
Dest, reinterpret_cast<const char *>(&std::get<Index>(T)),
|
|
|
|
sizeof(std::get<Index>(T)))) +
|
|
|
|
sizeof(std::get<Index>(T));
|
|
|
|
IndexedMemcpy<Index + 1>::Copy(Next, T);
|
|
|
|
}
|
|
|
|
|
|
|
|
template <
|
|
|
|
class Tuple,
|
|
|
|
typename std::enable_if<
|
|
|
|
(Index >=
|
|
|
|
std::tuple_size<typename std::remove_reference<Tuple>::type>::value),
|
|
|
|
int>::type = 0>
|
|
|
|
static void Copy(char *, Tuple &&) {}
|
|
|
|
};
|
|
|
|
|
2018-08-30 17:04:12 +08:00
|
|
|
template <uint8_t Kind, class... Values>
|
2018-08-31 18:03:52 +08:00
|
|
|
Error writeMetadata(raw_ostream &OS, Values &&... Ds) {
|
[XRay] FDRTraceWriter and FDR Trace Loading
Summary:
This is the first step in the larger refactoring and reduction of
D50441.
This step in the process does the following:
- Introduces more granular types of `Record`s representing the many
kinds of records written/read by the Flight Data Recorder (FDR) mode
`Trace` loading function(s).
- Introduces an abstract `RecordVisitor` type meant to handle the
processing of the various `Record` derived types. This `RecordVisitor`
has two implementations in this patch: `RecordInitializer` and
`FDRTraceWriter`.
- We also introduce a convenience interface for building a collection of
`Record` instances called a `LogBuilder`. This allows us to generate
sequences of `Record` instances manually (used in unit tests but
useful otherwise).
- The`FDRTraceWriter` class implements the `RecordVisitor` interface and
handles the writing of metadata records to a `raw_ostream`. We
demonstrate that in the unit test, we can generate in-memory FDR mode
traces using the specific `Record` derived types, which we load
through the `loadTrace(...)` function yielding valid `Trace` objects.
This patch introduces the required types and concepts for us to start
replacing the logic implemented in the `loadFDRLog` function to use the
more granular types. In subsequent patches, we will introduce more
visitor implementations which isolate the verification, printing,
indexing, production/consumption, and finally the conversion of the FDR
mode logs.
The overarching goal of these changes is to make handling FDR mode logs
better tested, more understandable, more extensible, and more
systematic. This will also allow us to better represent the execution
trace, as we improve the fidelity of the events we represent in an XRay
`Trace` object, which we intend to do after FDR mode log processing is
in better shape.
Reviewers: eizan
Reviewed By: eizan
Subscribers: mgorny, hiraditya, llvm-commits
Differential Revision: https://reviews.llvm.org/D51210
llvm-svn: 341029
2018-08-30 15:22:21 +08:00
|
|
|
MetadataBlob B;
|
|
|
|
B.Type = 1;
|
|
|
|
B.RecordKind = Kind;
|
2018-08-30 17:04:12 +08:00
|
|
|
std::memset(B.Data, 0, 15);
|
|
|
|
auto T = std::make_tuple(std::forward<Values>(std::move(Ds))...);
|
2018-08-30 16:15:42 +08:00
|
|
|
IndexedMemcpy<0>::Copy(B.Data, T);
|
[XRay] FDRTraceWriter and FDR Trace Loading
Summary:
This is the first step in the larger refactoring and reduction of
D50441.
This step in the process does the following:
- Introduces more granular types of `Record`s representing the many
kinds of records written/read by the Flight Data Recorder (FDR) mode
`Trace` loading function(s).
- Introduces an abstract `RecordVisitor` type meant to handle the
processing of the various `Record` derived types. This `RecordVisitor`
has two implementations in this patch: `RecordInitializer` and
`FDRTraceWriter`.
- We also introduce a convenience interface for building a collection of
`Record` instances called a `LogBuilder`. This allows us to generate
sequences of `Record` instances manually (used in unit tests but
useful otherwise).
- The`FDRTraceWriter` class implements the `RecordVisitor` interface and
handles the writing of metadata records to a `raw_ostream`. We
demonstrate that in the unit test, we can generate in-memory FDR mode
traces using the specific `Record` derived types, which we load
through the `loadTrace(...)` function yielding valid `Trace` objects.
This patch introduces the required types and concepts for us to start
replacing the logic implemented in the `loadFDRLog` function to use the
more granular types. In subsequent patches, we will introduce more
visitor implementations which isolate the verification, printing,
indexing, production/consumption, and finally the conversion of the FDR
mode logs.
The overarching goal of these changes is to make handling FDR mode logs
better tested, more understandable, more extensible, and more
systematic. This will also allow us to better represent the execution
trace, as we improve the fidelity of the events we represent in an XRay
`Trace` object, which we intend to do after FDR mode log processing is
in better shape.
Reviewers: eizan
Reviewed By: eizan
Subscribers: mgorny, hiraditya, llvm-commits
Differential Revision: https://reviews.llvm.org/D51210
llvm-svn: 341029
2018-08-30 15:22:21 +08:00
|
|
|
OS.write(reinterpret_cast<const char *>(&B), sizeof(MetadataBlob));
|
|
|
|
return Error::success();
|
|
|
|
}
|
|
|
|
|
|
|
|
} // namespace
|
|
|
|
|
|
|
|
FDRTraceWriter::FDRTraceWriter(raw_ostream &O, const XRayFileHeader &H)
|
|
|
|
: OS(O) {
|
|
|
|
// We need to re-construct a header, by writing the fields we care about for
|
|
|
|
// traces, in the format that the runtime would have written.
|
|
|
|
FileHeader Raw;
|
|
|
|
Raw.Version = H.Version;
|
|
|
|
Raw.Type = H.Type;
|
2018-08-31 18:03:52 +08:00
|
|
|
Raw.BitField = (H.ConstantTSC ? 0x01 : 0x0) | (H.NonstopTSC ? 0x02 : 0x0);
|
[XRay] FDRTraceWriter and FDR Trace Loading
Summary:
This is the first step in the larger refactoring and reduction of
D50441.
This step in the process does the following:
- Introduces more granular types of `Record`s representing the many
kinds of records written/read by the Flight Data Recorder (FDR) mode
`Trace` loading function(s).
- Introduces an abstract `RecordVisitor` type meant to handle the
processing of the various `Record` derived types. This `RecordVisitor`
has two implementations in this patch: `RecordInitializer` and
`FDRTraceWriter`.
- We also introduce a convenience interface for building a collection of
`Record` instances called a `LogBuilder`. This allows us to generate
sequences of `Record` instances manually (used in unit tests but
useful otherwise).
- The`FDRTraceWriter` class implements the `RecordVisitor` interface and
handles the writing of metadata records to a `raw_ostream`. We
demonstrate that in the unit test, we can generate in-memory FDR mode
traces using the specific `Record` derived types, which we load
through the `loadTrace(...)` function yielding valid `Trace` objects.
This patch introduces the required types and concepts for us to start
replacing the logic implemented in the `loadFDRLog` function to use the
more granular types. In subsequent patches, we will introduce more
visitor implementations which isolate the verification, printing,
indexing, production/consumption, and finally the conversion of the FDR
mode logs.
The overarching goal of these changes is to make handling FDR mode logs
better tested, more understandable, more extensible, and more
systematic. This will also allow us to better represent the execution
trace, as we improve the fidelity of the events we represent in an XRay
`Trace` object, which we intend to do after FDR mode log processing is
in better shape.
Reviewers: eizan
Reviewed By: eizan
Subscribers: mgorny, hiraditya, llvm-commits
Differential Revision: https://reviews.llvm.org/D51210
llvm-svn: 341029
2018-08-30 15:22:21 +08:00
|
|
|
Raw.CycleFrequency = H.CycleFrequency;
|
|
|
|
memcpy(&Raw.FreeForm, H.FreeFormData, 16);
|
|
|
|
OS.write(reinterpret_cast<const char *>(&Raw), sizeof(XRayFileHeader));
|
|
|
|
}
|
|
|
|
|
|
|
|
FDRTraceWriter::~FDRTraceWriter() {}
|
|
|
|
|
|
|
|
Error FDRTraceWriter::visit(BufferExtents &R) {
|
|
|
|
return writeMetadata<7u>(OS, R.size());
|
|
|
|
}
|
|
|
|
|
|
|
|
Error FDRTraceWriter::visit(WallclockRecord &R) {
|
|
|
|
return writeMetadata<4u>(OS, R.seconds(), R.nanos());
|
|
|
|
}
|
|
|
|
|
|
|
|
Error FDRTraceWriter::visit(NewCPUIDRecord &R) {
|
|
|
|
return writeMetadata<2u>(OS, R.cpuid());
|
|
|
|
}
|
|
|
|
|
|
|
|
Error FDRTraceWriter::visit(TSCWrapRecord &R) {
|
|
|
|
return writeMetadata<3u>(OS, R.tsc());
|
|
|
|
}
|
|
|
|
|
|
|
|
Error FDRTraceWriter::visit(CustomEventRecord &R) {
|
|
|
|
if (auto E = writeMetadata<5u>(OS, R.size(), R.tsc()))
|
|
|
|
return E;
|
|
|
|
OS.write(R.data().data(), R.data().size());
|
|
|
|
return Error::success();
|
|
|
|
}
|
|
|
|
|
|
|
|
Error FDRTraceWriter::visit(CallArgRecord &R) {
|
|
|
|
return writeMetadata<6u>(OS, R.arg());
|
|
|
|
}
|
|
|
|
|
|
|
|
Error FDRTraceWriter::visit(PIDRecord &R) {
|
|
|
|
return writeMetadata<9u>(OS, R.pid());
|
|
|
|
}
|
|
|
|
|
|
|
|
Error FDRTraceWriter::visit(NewBufferRecord &R) {
|
|
|
|
return writeMetadata<0u>(OS, R.tid());
|
|
|
|
}
|
|
|
|
|
|
|
|
Error FDRTraceWriter::visit(EndBufferRecord &R) {
|
|
|
|
return writeMetadata<1u>(OS, 0);
|
|
|
|
}
|
|
|
|
|
|
|
|
Error FDRTraceWriter::visit(FunctionRecord &R) {
|
|
|
|
FunctionDeltaBlob B;
|
|
|
|
B.Type = 0;
|
|
|
|
B.RecordKind = static_cast<uint8_t>(R.recordType());
|
|
|
|
B.FuncId = R.functionId();
|
|
|
|
B.TSCDelta = R.delta();
|
|
|
|
OS.write(reinterpret_cast<const char *>(&B), sizeof(FunctionDeltaBlob));
|
|
|
|
return Error::success();
|
|
|
|
}
|
|
|
|
|
|
|
|
} // namespace xray
|
|
|
|
} // namespace llvm
|