You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
weight: 1# Defines page ordering. Must be 1 for first (or only) page.
@@ -140,7 +138,7 @@ Verify the installation by checking the version:
140
138
./atperf version
141
139
```
142
140
143
-
The output displays the installed version number.
141
+
The output shows the installed version number:
144
142
145
143
```output
146
144
Arm Total Performance CLI version: 0.39.0
@@ -174,9 +172,9 @@ When the installation finishes, select **Close** to exit the installer.
174
172
175
173
Before connecting to an Arm Linux target, ensure SSH key-based authentication is configured and that passwordless sudo access is enabled. If you already manage your target system via SSH, you likely have most of this setup complete.
176
174
177
-
###Check your existing SSH key
175
+
## Check your existing SSH key
178
176
179
-
Verify that you can connect to your target using SSH:
177
+
Verify that you can connect to your target using SSH. Replace `user` with your username and `target_host` with your target's hostname or IP address:
If you're prompted for a passphrase, your key is protected with one. ATP doesn't support SSH keys with passphrases, so you need to create a separate key without a passphrase for ATP.
192
190
193
-
###Create a passphrase-free key for ATP (if needed)
191
+
## Create a passphrase-free key for ATP (if needed)
194
192
195
193
If your existing SSH key has a passphrase, generate a new key specifically for ATP:
196
194
@@ -212,9 +210,9 @@ If your existing key is in the default location (`~/.ssh/id_ed25519` or `~/.ssh/
You can now use `~/.ssh/atp_key` as the private key when configuring ATP's target connection.
213
+
You can now use `~/.ssh/atp_key` as the private key when configuring the ATP target connection.
216
214
217
-
###Enable passwordless sudo on the target
215
+
## Enable passwordless sudo on the target
218
216
219
217
ATP needs to run commands with elevated privileges on the target system. Because ATP cannot enter sudo passwords interactively, configure passwordless sudo access.
220
218
@@ -238,7 +236,7 @@ After installing ATP and preparing your target, you can connect using either the
238
236
239
237
### Connect using the ATP GUI
240
238
241
-
The GUI is typically used on Windows and macOS hosts, though it's also available on Linux.
239
+
Use the GUI on Windows and macOS hosts, though you can also run it on Linux.
242
240
243
241
Open the ATP application.
244
242
@@ -257,15 +255,15 @@ In the **Configure Target** form, provide the following details:
257
255
***Host Key Verification**: Choose **Strict** (recommended) or **Ignore**
258
256
* Strict mode verifies the server identity using your `~/.ssh/known_hosts` file
259
257
260
-

258
+

261
259
262
260
Select **Add Target**.
263
261
264
262
The target appears in the targets list and is ready for profiling.
265
263
266
264
You can select the **Test Connection** button to verify your connection to the ATP Linux target is successful.
267
265
268
-

266
+

269
267
270
268
#### Configure jump nodes (optional)
271
269
@@ -310,7 +308,7 @@ atperf --help
310
308
311
309
If your target is the same machine where you installed ATP (the host machine itself), ATP automatically provides a built-in `localhost` target. You don't need to configure authentication, SSH keys, or host verification for local profiling.
312
310
313
-
Verify the localhost target is available:
311
+
Verify the localhost target is available by listing all configured targets:
314
312
315
313
```bash
316
314
atperf target list
@@ -328,7 +326,7 @@ Your local machine is now ready to use as a target. Specify `--target=localhost`
328
326
329
327
#### Add a remote target
330
328
331
-
To profile a workload on a remote machine, add it as a target using the standard syntax:
329
+
To profile a workload on a remote machine, add it as a target using the standard syntax. This command registers the remote system with ATP:
0 commit comments