Merge branch 'amd-staging' into dgaliffi/sync-main-with-stg

Signed-off-by: David Galiffi <David.Galiffi@amd.com>

docs/archive/docs-1.x/analysis.md

@@ -171,7 +171,7 @@ $ omniperf analyze -p workloads/vcopy/mi200/ --list-metrics gfx90a
 ├─────────┼─────────────────────────────┤
 ...
  ```
- 2. Choose your own customized subset of metrics with `-b` (a.k.a. `--metric`), or build your own config following [config_template](https://github.com/ROCm/omniperf/blob/amd-mainline/src/omniperf_analyze/configs/panel_config_template.yaml). Below shows how to generate a report containing only metric 2 (a.k.a. System Speed-of-Light).
+ 2. Choose your own customized subset of metrics with `-b` (a.k.a. `--metric`), or build your own config following [config_template](https://github.com/ROCm/omniperf/blob/amd-mainline/src/rocprof_compute_analyze/configs/panel_config_template.yaml). Below shows how to generate a report containing only metric 2 (a.k.a. System Speed-of-Light).
 ```shell-session
 $ omniperf analyze -p workloads/vcopy/mi200/ -b 2
 --------
@@ -381,7 +381,7 @@ Analyze
 
 Dash is running on http://0.0.0.0:8050/
 
- * Serving Flask app 'omniperf_analyze.omniperf_analyze' (lazy loading)
+ * Serving Flask app 'rocprof_compute_analyze.rocprof_compute_analyze' (lazy loading)
  * Environment: production
    WARNING: This is a development server. Do not use it in a production deployment.
    Use a production WSGI server instead.
@@ -767,4 +767,4 @@ Most panels are designed around a specific IP block to thoroughly understand its
 ###### L2-EA Write Stalls
 ![L2-EA Write Stalls](images/L2_ea_write_stalls_per_channel.png)
 ###### L2-EA Write Starvation
-![L2-EA Write Starvation](images/L2_ea_write_starvation_per_channel.png)
+![L2-EA Write Starvation](images/L2_ea_write_starvation_per_channel.png)

docs/archive/docs-2.x/analysis.md

@@ -181,7 +181,7 @@ Analysis mode = cli
                 2.1.30 -> L1I Fetch Latency
 ...
 ```
-3. Choose your own customized subset of metrics with `-b` (a.k.a. `--block`), or build your own config following [config_template](https://github.com/ROCm/omniperf/blob/amd-mainline/src/omniperf_analyze/configs/panel_config_template.yaml). Below shows how to generate a report containing only metric 2 (a.k.a. System Speed-of-Light).
+3. Choose your own customized subset of metrics with `-b` (a.k.a. `--block`), or build your own config following [config_template](https://github.com/ROCm/omniperf/blob/amd-mainline/src/rocprof_compute_analyze/configs/panel_config_template.yaml). Below shows how to generate a report containing only metric 2 (a.k.a. System Speed-of-Light).
 ```shell-session
 $ omniperf analyze -p workloads/vcopy/MI200/ -b 2
 --------
@@ -407,7 +407,7 @@ Analysis mode = web_ui
 [analysis] deriving Omniperf metrics...
 Dash is running on http://0.0.0.0:8050/
 
- * Serving Flask app 'omniperf_analyze.analysis_webui' (lazy loading)
+ * Serving Flask app 'rocprof_compute_analyze.analysis_webui' (lazy loading)
  * Environment: production
    WARNING: This is a development server. Do not use it in a production deployment.
    Use a production WSGI server instead.

docs/how-to/analyze/cli.rst

@@ -186,7 +186,7 @@ Walkthrough
 
 3. Choose your own customized subset of metrics with the ``-b`` (or ``--block``)
    option. Or, build your own configuration following
-   `config_template <https://github.com/ROCm/omniperf/blob/amd-mainline/src/omniperf_soc/analysis_configs/panel_config_template.yaml>`_.
+   `config_template <https://github.com/ROCm/omniperf/blob/amd-mainline/src/rocprof_compute_soc/analysis_configs/panel_config_template.yaml>`_.
    The following snippet shows how to generate a report containing only metric 2
    (:doc:`System Speed-of-Light </conceptual/system-speed-of-light>`).
 

docs/how-to/analyze/standalone-gui.rst

@@ -47,7 +47,7 @@ desired analysis command. For example:
    [analysis] deriving Omniperf metrics...
    Dash is running on http://0.0.0.0:8050/
 
-    * Serving Flask app 'omniperf_analyze.analysis_webui' (lazy loading)
+    * Serving Flask app 'rocprof_compute_analyze.analysis_webui' (lazy loading)
     * Environment: production
       WARNING: This is a development server. Do not use it in a production deployment.
       Use a production WSGI server instead.

docs/sphinx/static/css/o_custom.css

@@ -1,8 +1,30 @@
+:root {
+    --amd-teal-500: #00C2DE;
+    --amd-teal-750: #00788E;
+}
+
 /* Override PyData Sphinx Theme default colors */
 html[data-theme='light'] {
+    --pst-color-primary: var(--amd-teal-750);
+    --pst-color-primary-bg: var(--amd-teal-500);
     --pst-color-table-row-hover-bg: #E2E8F0;
 }
 
 html[data-theme='dark'] {
+    --pst-color-primary: var(--amd-teal-500);
+    --pst-color-primary-bg: var(--amd-teal-750);
     --pst-color-table-row-hover-bg: #1E293B;
 }
+
+html[data-theme='light'],
+html[data-theme='dark'] {
+    --pst-color-link: var(--pst-color-primary);
+}
+
+a svg {
+  color: var(--pst-color-text-base);
+}
+
+a svg:hover {
+  color: var(--pst-color-link-hover);
+}