From 8d53e9f3c6001dcb2865f6e894da5b54e1418f88 Mon Sep 17 00:00:00 2001 From: Christian Ehrhardt Date: Thu, 4 Jul 2019 10:40:06 +0200 Subject: New upstream version 18.11.2 Change-Id: I23eb4f9179abf1f9c659891f8fddb27ee68ad26b Signed-off-by: Christian Ehrhardt --- doc/guides/prog_guide/profile_app.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/guides/prog_guide/profile_app.rst') diff --git a/doc/guides/prog_guide/profile_app.rst b/doc/guides/prog_guide/profile_app.rst index 02f05614..c1b29f93 100644 --- a/doc/guides/prog_guide/profile_app.rst +++ b/doc/guides/prog_guide/profile_app.rst @@ -64,7 +64,7 @@ The default ``cntvct_el0`` based ``rte_rdtsc()`` provides a portable means to get a wall clock counter in user space. Typically it runs at <= 100MHz. The alternative method to enable ``rte_rdtsc()`` for a high resolution wall -clock counter is through the armv8 PMU subsystem. The PMU cycle counter runs +clock counter is through the ARMv8 PMU subsystem. The PMU cycle counter runs at CPU frequency. However, access to the PMU cycle counter from user space is not enabled by default in the arm64 linux kernel. It is possible to enable cycle counter for user space access by configuring the PMU from the privileged @@ -75,7 +75,7 @@ scheme. Application can choose the PMU based implementation with ``CONFIG_RTE_ARM_EAL_RDTSC_USE_PMU``. The example below shows the steps to configure the PMU based cycle counter on -an armv8 machine. +an ARMv8 machine. .. code-block:: console -- cgit 1.2.3-korg