| .. | .. |
|---|
| 222 | 222 | way to request that counting of events be restricted to times when the |
|---|
| 223 | 223 | CPU is in user, kernel and/or hypervisor mode. |
|---|
| 224 | 224 | |
|---|
| 225 | +Furthermore the 'exclude_host' and 'exclude_guest' bits provide a way |
|---|
| 226 | +to request counting of events restricted to guest and host contexts when |
|---|
| 227 | +using Linux as the hypervisor. |
|---|
| 228 | + |
|---|
| 225 | 229 | The 'mmap' and 'munmap' bits allow recording of PROT_EXEC mmap/munmap |
|---|
| 226 | 230 | operations, these can be used to relate userspace IP addresses to actual |
|---|
| 227 | 231 | code, even after the mapping (or even the whole process) is gone, |
|---|
| .. | .. |
|---|
| 254 | 258 | their own tasks. |
|---|
| 255 | 259 | |
|---|
| 256 | 260 | A 'pid == -1' and 'cpu == x' counter is a per CPU counter that counts |
|---|
| 257 | | -all events on CPU-x. Per CPU counters need CAP_SYS_ADMIN privilege. |
|---|
| 261 | +all events on CPU-x. Per CPU counters need CAP_PERFMON or CAP_SYS_ADMIN |
|---|
| 262 | +privilege. |
|---|
| 258 | 263 | |
|---|
| 259 | 264 | The 'flags' parameter is currently unused and must be zero. |
|---|
| 260 | 265 | |
|---|