|
Revision tags: v24.05, v24.09-pre, v24.05-rc1 |
|
| #
23dbcec5 |
| 09-Feb-2024 |
Jim Harris <jim.harris@samsung.com> |
trace: merge spdk_trace_flags into spdk_trace_file
Signed-off-by: Jim Harris <jim.harris@samsung.com> Change-Id: I8a070f986825de2470d5873eaeed3849d36bf1af Reviewed-on: https://review.spdk.io/gerrit/
trace: merge spdk_trace_flags into spdk_trace_file
Signed-off-by: Jim Harris <jim.harris@samsung.com> Change-Id: I8a070f986825de2470d5873eaeed3849d36bf1af Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/21790 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Community-CI: Mellanox Build Bot Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
show more ...
|
|
Revision tags: LTS, v24.01, v24.05-pre, v24.01-rc1, v23.09, v24.01-pre, v23.09-rc1, v23.05, v23.09-pre, v23.01.1, v23.01, v23.05-pre, v23.01-rc1, v22.01.2, v22.09, v23.01-pre, v22.09-rc1, v22.05, v22.09-pre, v22.05-rc1, v22.01.1, v22.01, v22.01-rc1, v21.10, v21.10-rc1 |
|
| #
189b0f09 |
| 14-Sep-2021 |
Konrad Sztyber <konrad.sztyber@intel.com> |
lib/trace_parser: method for retrieving entry count
Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: If5f1b1bea0d30419be46e704ddd7c2f9556b4627 Reviewed-on: https://review.spdk.io/
lib/trace_parser: method for retrieving entry count
Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: If5f1b1bea0d30419be46e704ddd7c2f9556b4627 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9498 Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Reviewed-by: Krzysztof Karas <krzysztof.karas@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>
show more ...
|
| #
279b7bab |
| 31-Aug-2021 |
Konrad Sztyber <konrad.sztyber@intel.com> |
lib/trace_parser: method for iterating over entries
Added a definition of a parsed trace entry and a function allowing for iterating over these objects. The difference between a parsed and a regula
lib/trace_parser: method for iterating over entries
Added a definition of a parsed trace entry and a function allowing for iterating over these objects. The difference between a parsed and a regular trace entry is that it includes more information gathered while processing the trace file (e.g. lcore, object statistics) and provides a contigous buffer for trace arguments.
For now, only lcore and the pointer to the actual trace entry are filled. Tracepoint arguments and object statistics will be added in subsequent patches.
Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: I4d5e30a7abb4860a5ba9db46f64ceae8bd14646f Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9433 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com>
show more ...
|
| #
6727cc38 |
| 31-Aug-2021 |
Konrad Sztyber <konrad.sztyber@intel.com> |
lib/trace_parser: method for retrieving tsc offset
Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: I11fc341b4353c01cd933d6692cf97de3a3744a84 Reviewed-on: https://review.spdk.io/g
lib/trace_parser: method for retrieving tsc offset
Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: I11fc341b4353c01cd933d6692cf97de3a3744a84 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9432 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com>
show more ...
|
| #
41ba2b30 |
| 31-Aug-2021 |
Konrad Sztyber <konrad.sztyber@intel.com> |
lib/trace_parser: method for retrieving trace flags
It gives user access to things like the tsc rate and tracepoint definitions.
Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id:
lib/trace_parser: method for retrieving trace flags
It gives user access to things like the tsc rate and tracepoint definitions.
Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: Ib50126b331faa4508174c7cb707643a3d8db6a01 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9430 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com>
show more ...
|
| #
d919a197 |
| 30-Aug-2021 |
Konrad Sztyber <konrad.sztyber@intel.com> |
lib/trace_parser: add trace_parser library stubs
This library will provide functions that parse traces recorded by an SPDK application. This includes merging traces from multiple cores, sorting the
lib/trace_parser: add trace_parser library stubs
This library will provide functions that parse traces recorded by an SPDK application. This includes merging traces from multiple cores, sorting them by their timestamp and constructing trace entries spanning across multiple buffers. All of these tasks are currently implemented in the spdk_trace app, so most of its code will be moved here (this is the reason for using C++).
The motivation for extracting this code to a library is to be able to use it from places other than the spdk_trace app, specifically the `scripts/bpf/trace.py` script.
The main reason for creating a separate library instead of extending libtrace is to avoid pulling in all of its dependencies. ISA-L is the most problematic, as we only build it as a static library, which makes it impossible to use with dlopen (making it unusable in scripts).
Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: If101ca3425d7404abd51b0da2031358d0be44766 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/9428 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@mellanox.com>
show more ...
|