Searched refs:logs (Results 1 – 19 of 19) sorted by relevance
| /dpdk/.github/workflows/ |
| H A D | build.yml | 149 - name: Upload logs on failure
153 name: meson-logs-${{ join(matrix.config.*, '-') }}
157 build/meson-logs/meson-log.txt
158 build/meson-logs/testlog.txt
240 echo -n '::set-output name=logs::'
241 echo 'meson-logs-${{ join(matrix.config.*, '-') }}' | tr -d ':'
289 - name: Upload logs on failure
293 name: ${{ steps.get_keys.outputs.logs }}
296 build/meson-logs/meson-log.txt
|
| /dpdk/doc/guides/rawdevs/ |
| H A D | dpaa2_cmdif.rst | 42 Enabling logs
45 For enabling logs, use the following EAL parameter:
51 Using ``pmd.raw.dpaa2.cmdif`` as log matching criteria, all Event PMD logs can be
|
| H A D | dpaa2_qdma.rst | 46 Enabling logs
49 For enabling logs, use the following EAL parameter:
55 Using ``pmd.raw.dpaa2.qdma`` as log matching criteria, all Event PMD logs can be
|
| /dpdk/doc/guides/eventdevs/ |
| H A D | dpaa2.rst | 65 Enabling logs
68 For enabling logs, use the following EAL parameter:
74 Using ``eventdev.dpaa2`` as log matching criteria, all Event PMD logs can be
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | dpaa_sec.rst | 115 Enabling logs
118 For enabling logs, use the following EAL parameter:
124 Using ``pmd.crypto.dpaa`` as log matching criteria, all Crypto PMD logs can be
|
| H A D | dpaa2_sec.rst | 167 Enabling logs
170 For enabling logs, use the following EAL parameter:
176 Using ``crypto.dpaa2`` as log matching criteria, all Crypto PMD logs can be
|
| H A D | caam_jr.rst | 113 Enabling logs
116 For enabling logs, use the following EAL parameter:
|
| H A D | qat.rst | 452 to load MMP firmware qat_895xcc_mmp.bin`` in kernel logs, this may be as a
|
| /dpdk/doc/guides/bbdevs/ |
| H A D | la12xx.rst | 70 Enabling logs
73 For enabling logs, use the following EAL parameter:
79 Using ``bb.la12xx`` as log matching criteria, all Baseband PMD logs can be
|
| /dpdk/doc/guides/nics/ |
| H A D | af_xdp.rst | 171 the following logs will appear when an application is launched:
178 These logs are not errors and can be ignored.
|
| H A D | dpaa2.rst | 491 Enabling logs
500 Using ``bus.fslmc`` as log matching criteria, all FSLMC bus logs can be enabled
509 Using ``pmd.net.dpaa2`` as log matching criteria, all PMD logs can be enabled
|
| H A D | bnx2x.rst | 112 be held by configured mbuf size and logs the message.
|
| /dpdk/doc/guides/windows_gsg/ |
| H A D | run_apps.rst | 57 on initialization (debug-level logs provide more details):
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | dist_app.rst | 126 the line "#define DEBUG" defined in start of the application in main.c to enable debug logs.
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | trace_lib.rst | 182 any type of logs or traces, including DPDK traces.
|
| H A D | env_abstraction_layer.rst | 426 By default, in a Linux application, logs are sent to syslog and also to the console.
|
| /dpdk/doc/guides/contributing/ |
| H A D | coding_style.rst | 717 /* enable all PMD logs (whose identifier string starts with "pmd.") */
829 difference between initialization code, and logs of events that occur at runtime.
842 the remaining driver logs ``pmd.net.i40e.driver``.
|
| H A D | unit_test.rst | 387 in the `build/meson-logs/coveragereport/` directory
|
| H A D | patches.rst | 460 Then the git logs should be checked using the ``check-git-log.sh`` script.
|