Translation Source string Target string
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
Using operf
Memakai operf
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
Using operf
Usando operf
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
Using operf
operf 사용하기
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
[command]#operf# is the recommended profiling mode that does not require initial setup before starting. All settings are specified as command-line options and there is no separate command to start the profiling process. To stop [command]#operf#, press Ctrl+C. The typical [command]#operf# command syntax looks as follows:
[command]#operf# is the recommended profiling mode that does not require initial setup before starting. All settings are specified as command-line options and there is no separate command to start the profiling process. To stop [command]#operf#, press Ctrl+C. The typical [command]#operf# command syntax looks as follows:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
[command]#operf# is the recommended profiling mode that does not require initial setup before starting. All settings are specified as command-line options and there is no separate command to start the profiling process. To stop [command]#operf#, press Ctrl+C. The typical [command]#operf# command syntax looks as follows:
[command]#operf# adalah mode pembuatan profil yang direkomendasikan yang tidak memerlukan pengaturan awal sebelum memulai. Semua pengaturan ditentukan sebagai opsi baris perintah dan tidak ada perintah terpisah untuk memulai proses pembuatan profil. Untuk menghentikan [command]#operf#, tekan Ctrl+C. Sintaks perintah khas [command]#operf# terlihat sebagai berikut:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
[command]#operf# is the recommended profiling mode that does not require initial setup before starting. All settings are specified as command-line options and there is no separate command to start the profiling process. To stop [command]#operf#, press Ctrl+C. The typical [command]#operf# command syntax looks as follows:
[command]#operf# es el modo de perfilado recomendado que no requiere ajusta inicial antes de arrancar. Todos los ajustes son especificado como opciones de línea de comando y no hay un comando separado para arrancar el proceso de perfilado. Para parar [command]#operf#, presiones Ctrl+C. La sintaxis típica del comando [command]#operf# se ve como sigue:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
[command]#operf# _options_ _range_ _command_ _args_
[command]#operf# _options_ _range_ _command_ _args_
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
[command]#operf# _options_ _range_ _command_ _args_
[command]#operf# _opsis_ _rentang_ _perintah_ _argumen_
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
[command]#operf# _options_ _range_ _command_ _args_
[command]#operf# _options_ _range_ _command_ _args_
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
[command]#operf# _options_ _range_ _command_ _args_
[command]#operf# _옵션_ _범위_ _명령_ _인수_
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Replace _options_ with the desired command-line options to specify your profiling settings. Full set of options is described in `operf(1)` manual page. Replace _range_ with one of the following:
Replace _options_ with the desired command-line options to specify your profiling settings. Full set of options is described in `operf(1)` manual page. Replace _range_ with one of the following:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
Replace _options_ with the desired command-line options to specify your profiling settings. Full set of options is described in `operf(1)` manual page. Replace _range_ with one of the following:
Reemplace _options_ con las opciones de línea de comando deseadas para especificar sus ajustes de perfilado. El conjunto completo de las opciones se describe en la página de manual `operf(1)`. Reemplace _range_ con uno de lo siguiente:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
[option]`--system-wide` - this setting allows for global profiling, see xref:OProfile.adoc#using_operf_system-wide[Using [command]#operf# in System-wide Mode] +
[option]`--system-wide` - this setting allows for global profiling, see xref:OProfile.adoc#using_operf_system-wide[Using [command]#operf# in System-wide Mode] +
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
[option]`--system-wide` - this setting allows for global profiling, see xref:OProfile.adoc#using_operf_system-wide[Using [command]#operf# in System-wide Mode] +
[option]`--system-wide` - este ajuste permite la creación de perfiles globales, vea xref:OProfile.adoc#using_operf_system-wide[Using [command]#operf# en Modo Todo el Sistema] +
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
[option]`--pid=pass:attributes[{blank}]_PID_pass:attributes[{blank}]` - this is to profile a running application, where _PID_ is the process ID of the process you want to profile. +
[option]`--pid=pass:attributes[{blank}]_PID_pass:attributes[{blank}]` - this is to profile a running application, where _PID_ is the process ID of the process you want to profile. +
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
[option]`--pid=pass:attributes[{blank}]_PID_pass:attributes[{blank}]` - this is to profile a running application, where _PID_ is the process ID of the process you want to profile. +
[option]`--pid=pass:attributes[{blank}]_PID_pass:attributes[{blank}]` - esto es para establecer perfil en una aplicación en ejecución, donde _PID_ es la ID del proceso en el que desea establecer perfil. +
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
With _command_ and _args_, you can define a specific command or application to be profiled, and also the input arguments that this command or application requires. Either _command_, [option]`--pid` or [option]`--system-wide` is required, but these cannot be used simultaneously.
With _command_ and _args_, you can define a specific command or application to be profiled, and also the input arguments that this command or application requires. Either _command_, [option]`--pid` or [option]`--system-wide` is required, but these cannot be used simultaneously.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
With _command_ and _args_, you can define a specific command or application to be profiled, and also the input arguments that this command or application requires. Either _command_, [option]`--pid` or [option]`--system-wide` is required, but these cannot be used simultaneously.
Con _command_ y _args_, usted puede definir un comando o aplicación específica donde establecer un perfil y también los argumentos de entrada que requiere ese comando o aplicación. Se requiere o _command_, [option]`--pid` o [option]`--system-wide`, pero no pueden ser usados simultáneamente.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
When you invoke [command]#operf# on a command line without setting the _range_ option, data will be collected for the children processes.
When you invoke [command]#operf# on a command line without setting the _range_ option, data will be collected for the children processes.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
When you invoke [command]#operf# on a command line without setting the _range_ option, data will be collected for the children processes.
Cuando invoca [command]#operf# en la línea de comando sin establecer la opción _range_, los datos serán recogidos de los procesos hijos.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Using [command]#operf# in System-wide Mode
Using [command]#operf# in System-wide Mode
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
Using [command]#operf# in System-wide Mode
Usando [command]#operf# en Modo Todo el Sistema
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
Using [command]#operf# in System-wide Mode
시스템-전반에 걸친 방식에서 [command]#operf# 사용하기
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
To run [command]#operf# [option]`--system-wide`, you need `root` authority. When finished profiling, you can stop [command]#operf# with `Ctrl+C`.
To run [command]#operf# [option]`--system-wide`, you need `root` authority. When finished profiling, you can stop [command]#operf# with `Ctrl+C`.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
To run [command]#operf# [option]`--system-wide`, you need `root` authority. When finished profiling, you can stop [command]#operf# with `Ctrl+C`.
Para ejecutar [command]#operf# [option]`--system-wide`, usted necesita autoridad de `root`. Cuando termine de perfilar, puede parar [command]#operf# con `Ctrl+C`.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
If you run [command]#operf# [option]`--system-wide` as a background process (with `&`), stop it in a controlled manner in order to process the collected profile data. For this purpose, use:
If you run [command]#operf# [option]`--system-wide` as a background process (with `&`), stop it in a controlled manner in order to process the collected profile data. For this purpose, use:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
If you run [command]#operf# [option]`--system-wide` as a background process (with `&`), stop it in a controlled manner in order to process the collected profile data. For this purpose, use:
Si ejecuta [command]#operf# [option]`--system-wide` como proceso en segundo plano (con `&`), párelo de manera controlado con el objetivo de que el proceso recoja los datos de pérfil. Para este propósito, utilice:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
[command]#kill -SIGINT operf-PID#
[command]#kill -SIGINT operf-PID#
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
[command]#kill -SIGINT operf-PID#
[command]#kill -SIGINT operf-PID#
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
When running [command]#operf# [option]`--system-wide`, it is recommended that your current working directory is `/root` or a subdirectory of `/root` so that sample data files are not stored in locations accessible by regular users.
When running [command]#operf# [option]`--system-wide`, it is recommended that your current working directory is `/root` or a subdirectory of `/root` so that sample data files are not stored in locations accessible by regular users.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
When running [command]#operf# [option]`--system-wide`, it is recommended that your current working directory is `/root` or a subdirectory of `/root` so that sample data files are not stored in locations accessible by regular users.
Cuando esté corriendo [command]#operf# [option]`--system-wide`, se recomienda que su directorio de trabajo sea `/root` o un subdirectorio de `/root` de modo que los archivos de datos de muestra no se almacenen en localizaciones accesibles para usuarios regulares.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Specifying the Kernel
Specifying the Kernel
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
Specifying the Kernel
Menentukan Kernel
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
Specifying the Kernel
Especificando el Kernel
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
Specifying the Kernel
커널 지정하기
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
To monitor the kernel, execute the following command:
To monitor the kernel, execute the following command:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
To monitor the kernel, execute the following command:
Para monitorizar el kernel, ejecute el siguiente comando:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
To monitor the kernel, execute the following command:
커널을 모니터 하려면, 다음 명령어를 실행하세요:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
operf --vmlinux=pass:quotes[_vmlinux_path_]
operf --vmlinux=pass:quotes[_vmlinux_path_]
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
operf --vmlinux=pass:quotes[_vmlinux_path_]
operf --vmlinux=pass:quotes[_vmlinux_path_]
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
operf --vmlinux=pass:quotes[_vmlinux_path_]
operf --vmlinux=pass:quotes[_vmlinux_path_]
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
operf --vmlinux=pass:quotes[_vmlinux_path_]
operf --vmlinux=pass:quotes[_vmlinux_path_]
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
With this option, you can specify a path to a vmlinux file that matches the running kernel. Kernel samples will be attributed to this binary, allowing post-processing tools to attribute samples to the appropriate kernel symbols. If this option is not specified, all kernel samples will be attributed to a pseudo binary named "no-vmlinux".
With this option, you can specify a path to a vmlinux file that matches the running kernel. Kernel samples will be attributed to this binary, allowing post-processing tools to attribute samples to the appropriate kernel symbols. If this option is not specified, all kernel samples will be attributed to a pseudo binary named "no-vmlinux".
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
With this option, you can specify a path to a vmlinux file that matches the running kernel. Kernel samples will be attributed to this binary, allowing post-processing tools to attribute samples to the appropriate kernel symbols. If this option is not specified, all kernel samples will be attributed to a pseudo binary named "no-vmlinux".
Con esta opción puede especificar una ruta a un archivo vmlinux que coincida con el kernel que está corriendo. Las muestras del kernel serán atribuidas a este binario permitiendo que las herramientas de pos procesado atribuir las muestras a los símbolos apropiados del kernel. Si no se especifica esta opción todas las muestras del kernel se atribuyen a un pseudobinario llamado "no-vmlinux".
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Setting Events to Monitor
Setting Events to Monitor
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
Setting Events to Monitor
Mengatur Kejadian yang Dipantau
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Spanish
Setting Events to Monitor
Ajustando Eventos a Monitorizar
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
Setting Events to Monitor
모니터 하려는 사건 설정
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Most processors contain counters, which are used by OProfile to monitor specific events. As shown in xref:OProfile.adoc#tb-oprofile-processors[OProfile Processors and Counters], the number of counters available depends on the processor.
Most processors contain counters, which are used by OProfile to monitor specific events. As shown in xref:OProfile.adoc#tb-oprofile-processors[OProfile Processors and Counters], the number of counters available depends on the processor.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
The events for each counter can be configured via the command line or with a graphical interface. For more information on the graphical interface, see xref:OProfile.adoc#s1-oprofile-gui[Graphical Interface]. If the counter cannot be set to a specific event, an error message is displayed.
The events for each counter can be configured via the command line or with a graphical interface. For more information on the graphical interface, see xref:OProfile.adoc#s1-oprofile-gui[Graphical Interface]. If the counter cannot be set to a specific event, an error message is displayed.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Older Processors and operf
Older Processors and operf
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
Older Processors and operf
이전 프로세서와 operf
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Some older processor models are not supported by the underlying Linux Performance Events Subsystem kernel and therefore are not supported by [command]#operf#. If you receive this message:
Some older processor models are not supported by the underlying Linux Performance Events Subsystem kernel and therefore are not supported by [command]#operf#. If you receive this message:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Your kernel's Performance Events Subsystem does not support your processor type
Your kernel's Performance Events Subsystem does not support your processor type
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
when attempting to use [command]#operf#, try profiling with [command]#opcontrol# to see if your processor type may be supported by OProfile's legacy mode.
when attempting to use [command]#operf#, try profiling with [command]#opcontrol# to see if your processor type may be supported by OProfile's legacy mode.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Using operf on Virtual Systems
Using operf on Virtual Systems
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
Using operf on Virtual Systems
Menggunakan operf pada Sistem Virtual
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
Using operf on Virtual Systems
가상 시스템에서 operf 사용하기
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Since hardware performance counters are not available on guest virtual machines, you have to enable *timer* mode to use [application]*operf* on virtual systems. To do so, type as `root`:
Since hardware performance counters are not available on guest virtual machines, you have to enable *timer* mode to use [application]*operf* on virtual systems. To do so, type as `root`:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
[command]#opcontrol# [option]`--deinit`
[command]#opcontrol# [option]`--deinit`
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
[command]#opcontrol# [option]`--deinit`
[command]#opcontrol# [option]`--deinit`
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
[command]#opcontrol# [option]`--deinit`
[command]#opcontrol# [option]`--deinit`
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
[command]#modprobe# [command]#oprofile# [option]`timer=1`
[command]#modprobe# [command]#oprofile# [option]`timer=1`
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
[command]#modprobe# [command]#oprofile# [option]`timer=1`
[command]#modprobe# [command]#oprofile# [option]`timer=1`
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
[command]#modprobe# [command]#oprofile# [option]`timer=1`
[command]#modprobe# [command]#oprofile# [option]`timer=1`
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
To set the event for each configurable counter via the command line, use:
To set the event for each configurable counter via the command line, use:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
To set the event for each configurable counter via the command line, use:
입력줄을 통해 각 구성 가능한 카운터를 위한 사건을 설정하려면, 다음을 사용하세요:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
[command]#operf# [option]`--events`pass:attributes[{blank}]=pass:attributes[{blank}]_event1_,_event2_pass:attributes[{blank}]…
[command]#operf# [option]`--events`pass:attributes[{blank}]=pass:attributes[{blank}]_event1_,_event2_pass:attributes[{blank}]…
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
[command]#operf# [option]`--events`pass:attributes[{blank}]=pass:attributes[{blank}]_event1_,_event2_pass:attributes[{blank}]…
[command]#operf# [option]`--events`pass:attributes[{blank}]=pass:attributes[{blank}]_event1_,_event2_pass:attributes[{blank}]…
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
[command]#operf# [option]`--events`pass:attributes[{blank}]=pass:attributes[{blank}]_event1_,_event2_pass:attributes[{blank}]…
[command]#operf# [option]`--events`pass:attributes[{blank}]=pass:attributes[{blank}]_event1_,_event2_pass:attributes[{blank}]…
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Here, pass a comma-separated list of event specifications for profiling. Each event specification is a colon-separated list of attributes in the following form:
Here, pass a comma-separated list of event specifications for profiling. Each event specification is a colon-separated list of attributes in the following form:
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
_event-name_:pass:attributes[{blank}]_sample-rate_:pass:attributes[{blank}]_unit-mask_:pass:attributes[{blank}]_kernel_:pass:attributes[{blank}]_user_
_event-name_:pass:attributes[{blank}]_sample-rate_:pass:attributes[{blank}]_unit-mask_:pass:attributes[{blank}]_kernel_:pass:attributes[{blank}]_user_
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
_event-name_:pass:attributes[{blank}]_sample-rate_:pass:attributes[{blank}]_unit-mask_:pass:attributes[{blank}]_kernel_:pass:attributes[{blank}]_user_
_event-name_:pass:attributes[{blank}]_sample-rate_:pass:attributes[{blank}]_unit-mask_:pass:attributes[{blank}]_kernel_:pass:attributes[{blank}]_user_
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
_event-name_:pass:attributes[{blank}]_sample-rate_:pass:attributes[{blank}]_unit-mask_:pass:attributes[{blank}]_kernel_:pass:attributes[{blank}]_user_
_event-name_:pass:attributes[{blank}]_sample-rate_:pass:attributes[{blank}]_unit-mask_:pass:attributes[{blank}]_kernel_:pass:attributes[{blank}]_user_
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
xref:OProfile.adoc#tab_event_specifications[Event Specifications] summarizes these options. The last three values are optional, if you omit them, they will be set to their default values. Note that certain events do require a unit mask.
xref:OProfile.adoc#tab_event_specifications[Event Specifications] summarizes these options. The last three values are optional, if you omit them, they will be set to their default values. Note that certain events do require a unit mask.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Event Specifications
Event Specifications
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
Event Specifications
Spesifikasi Kejadian
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
Event Specifications
사건 사양
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
|Specification|Description
|_event-name_|The exact symbolic event name taken from [command]#ophelp#
|_sample-rate_|The number of events to wait before sampling again. The smaller the count, the more frequent the samples. For events that do not happen frequently, a lower count may be needed to capture a statistically significant number of event instances. On the other hand, sampling too frequently can overload the system. By default, OProfile uses a time-based event set, which creates a sample every 100,000 clock cycles per processor.
|_unit-mask_|Unit masks, which further define the event, are listed in [command]#ophelp#.
You can insert either a hexadecimal value, beginning with "0x", or a string that matches the first word of the unit mask description in [command]#ophelp#. Definition by name is valid only for unit masks having "extra:" parameters, as shown by the output of [command]#ophelp#. This type of unit mask cannot be defined with a hexadecimal value. Note that on certain architectures, there can be multiple unit masks with the same hexadecimal value. In that case they have to be specified by their names only.
|_kernel_|Specifies whether to profile kernel code (insert `0` or `1`(default))
|_user_|Specifies whether to profile user-space code (insert `0` or `1` (default))
|Specification|Description
|_event-name_|The exact symbolic event name taken from [command]#ophelp#
|_sample-rate_|The number of events to wait before sampling again. The smaller the count, the more frequent the samples. For events that do not happen frequently, a lower count may be needed to capture a statistically significant number of event instances. On the other hand, sampling too frequently can overload the system. By default, OProfile uses a time-based event set, which creates a sample every 100,000 clock cycles per processor.
|_unit-mask_|Unit masks, which further define the event, are listed in [command]#ophelp#.
You can insert either a hexadecimal value, beginning with "0x", or a string that matches the first word of the unit mask description in [command]#ophelp#. Definition by name is valid only for unit masks having "extra:" parameters, as shown by the output of [command]#ophelp#. This type of unit mask cannot be defined with a hexadecimal value. Note that on certain architectures, there can be multiple unit masks with the same hexadecimal value. In that case they have to be specified by their names only.
|_kernel_|Specifies whether to profile kernel code (insert `0` or `1`(default))
|_user_|Specifies whether to profile user-space code (insert `0` or `1` (default))
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
|Specification|Description
|_event-name_|The exact symbolic event name taken from [command]#ophelp#
|_sample-rate_|The number of events to wait before sampling again. The smaller the count, the more frequent the samples. For events that do not happen frequently, a lower count may be needed to capture a statistically significant number of event instances. On the other hand, sampling too frequently can overload the system. By default, OProfile uses a time-based event set, which creates a sample every 100,000 clock cycles per processor.
|_unit-mask_|Unit masks, which further define the event, are listed in [command]#ophelp#.
You can insert either a hexadecimal value, beginning with "0x", or a string that matches the first word of the unit mask description in [command]#ophelp#. Definition by name is valid only for unit masks having "extra:" parameters, as shown by the output of [command]#ophelp#. This type of unit mask cannot be defined with a hexadecimal value. Note that on certain architectures, there can be multiple unit masks with the same hexadecimal value. In that case they have to be specified by their names only.
|_kernel_|Specifies whether to profile kernel code (insert `0` or `1`(default))
|_user_|Specifies whether to profile user-space code (insert `0` or `1` (default))
|사양|설명
|_event-name_|The exact symbolic event name taken from [command]#ophelp#
|_sample-rate_|The number of events to wait before sampling again. The smaller the count, the more frequent the samples. For events that do not happen frequently, a lower count may be needed to capture a statistically significant number of event instances. On the other hand, sampling too frequently can overload the system. By default, OProfile uses a time-based event set, which creates a sample every 100,000 clock cycles per processor.
|_unit-mask_|Unit masks, which further define the event, are listed in [command]#ophelp#.
You can insert either a hexadecimal value, beginning with "0x", or a string that matches the first word of the unit mask description in [command]#ophelp#. Definition by name is valid only for unit masks having "extra:" parameters, as shown by the output of [command]#ophelp#. This type of unit mask cannot be defined with a hexadecimal value. Note that on certain architectures, there can be multiple unit masks with the same hexadecimal value. In that case they have to be specified by their names only.
|_kernel_|Specifies whether to profile kernel code (insert `0` or `1`(default))
|_user_|Specifies whether to profile user-space code (insert `0` or `1` (default))
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
The events available vary depending on the processor type. When no event specification is given, the default event for the running processor type will be used for profiling. See xref:OProfile.adoc#tb-oprofile-default-events[Default Events] for a list of these default events. To determine the events available for profiling, use the [command]#ophelp# command.
The events available vary depending on the processor type. When no event specification is given, the default event for the running processor type will be used for profiling. See xref:OProfile.adoc#tb-oprofile-default-events[Default Events] for a list of these default events. To determine the events available for profiling, use the [command]#ophelp# command.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
[command]#ophelp#
[command]#ophelp#
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
[command]#ophelp#
[command]#ophelp#
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
[command]#ophelp#
[command]#ophelp#
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Categorization of Samples
Categorization of Samples
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
Categorization of Samples
견본 분류
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
The [option]`--separate-thread` option categorizes samples by thread group ID (tgid) and thread ID (tid). This is useful for seeing per-thread samples in multi-threaded applications. When used in conjunction with the [option]`--system-wide` option, [option]`--separate-thread` is also useful for seeing per-process (i.e., per-thread group) samples for the case where multiple processes are executing the same program during a profiling run.
The [option]`--separate-thread` option categorizes samples by thread group ID (tgid) and thread ID (tid). This is useful for seeing per-thread samples in multi-threaded applications. When used in conjunction with the [option]`--system-wide` option, [option]`--separate-thread` is also useful for seeing per-process (i.e., per-thread group) samples for the case where multiple processes are executing the same program during a profiling run.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
The [option]`--separate-cpu` option categorizes samples by CPU.
The [option]`--separate-cpu` option categorizes samples by CPU.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
The [option]`--separate-cpu` option categorizes samples by CPU.
[option]`--separate-cpu` 선택은 CPU 별로 견본을 분류합니다.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Configuring OProfile Using Legacy Mode
Configuring OProfile Using Legacy Mode
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
Configuring OProfile Using Legacy Mode
기존 방법을 사용하여 O프로파일 구성하기
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
indexterm:[OProfile,configuring]indexterm:[OProfile,opcontrol]indexterm:[opcontrol,OProfile] Before OProfile can be run in legacy mode, it must be configured. At a minimum, selecting to monitor the kernel (or selecting not to monitor the kernel) is required. The following sections describe how to use the [command]#opcontrol# utility to configure OProfile. As the [command]#opcontrol# commands are executed, the setup options are saved to the `/root/.oprofile/daemonrc` file.
indexterm:[OProfile,configuring]indexterm:[OProfile,opcontrol]indexterm:[opcontrol,OProfile] Before OProfile can be run in legacy mode, it must be configured. At a minimum, selecting to monitor the kernel (or selecting not to monitor the kernel) is required. The following sections describe how to use the [command]#opcontrol# utility to configure OProfile. As the [command]#opcontrol# commands are executed, the setup options are saved to the `/root/.oprofile/daemonrc` file.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
indexterm:[OProfile,monitoring the kernel] First, configure whether OProfile should monitor the kernel. This is the only configuration option that is required before starting OProfile. All others are optional.
indexterm:[OProfile,monitoring the kernel] First, configure whether OProfile should monitor the kernel. This is the only configuration option that is required before starting OProfile. All others are optional.
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
To monitor the kernel, execute the following command as `root`: indexterm:[OProfile,opcontrol,--vmlinux=]
To monitor the kernel, execute the following command as `root`: indexterm:[OProfile,opcontrol,--vmlinux=]
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
To monitor the kernel, execute the following command as `root`: indexterm:[OProfile,opcontrol,--vmlinux=]
커널을 모니터 하려면, `root`으로 다음 명령을 실행합니다:[O프로파일,opcontrol,--vmlinux=]
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
~]# opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux
~]# opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Indonesian
~]# opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux
~]# opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
~]# opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux
~]# opcontrol --setup --vmlinux=/usr/lib/debug/lib/modules/`uname -r`/vmlinux
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — English
Install the debuginfo package
Install the debuginfo package
fedora-docs-l10n/fedora-system-administrat/f26/pages/monitoring-and-automation/OProfile — Korean
Install the debuginfo package
디버그정보 꾸러미 설치