Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow launching perf on remote machines #12

Open
milianw opened this issue Dec 23, 2016 · 4 comments · May be fixed by #359
Open

allow launching perf on remote machines #12

milianw opened this issue Dec 23, 2016 · 4 comments · May be fixed by #359

Comments

@milianw
Copy link
Member

milianw commented Dec 23, 2016

Extend the feature in #11 to allow running perf on a remote machine via ssh, then stream the data to localhost

@tmcguire
Copy link
Contributor

It would be nice if hotspot can help with the setup here, which might not be easy for novice users. Especially setting up debug symbols, which might only be available on the host's sysroot.

@jonhoo
Copy link

jonhoo commented Jul 3, 2017

Presumably another thing that would be needed here would be to supply a symbol file other than the one named in perf.data, as the binary may reside at a different location locally.

@milianw
Copy link
Member Author

milianw commented Jul 4, 2017

@jonhoo not sure, but I think what you mention is implemented already. Have a look at the command line arguments, cf.:

$ hotspot --help
Usage: hotspot [options] [files...]
Linux perf GUI for performance analysis.

Options:
  -h, --help               Displays this help.
  -v, --version            Displays version information.
  --sysroot <path>         Path to sysroot which is used to find libraries.
  --kallsyms <path>        Path to kallsyms file which is used to resolve
                           kernel symbols.
  --debugPaths <paths>     Colon separated list of paths that contain debug
                           information.
  --extraLibPaths <paths>  Colon separated list of extra paths to find
                           libraries.
  --appPath <path>         Path to folder containing the application executable
                           and libraries.
  --arch <path>            Architecture to use for unwinding.

Arguments:
  files                    Optional input files to open on startup, i.e.
                           perf.data files

@jonhoo
Copy link

jonhoo commented Jul 4, 2017

Ah, yes, you're right. My bad for not digging a bit further.

@jeff-dagenais jeff-dagenais linked a pull request Oct 5, 2022 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants