oprofile: introduce module parameter oprofile.cpu_type
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest2 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | oprofile: introduce module_param oprofile.cpu_typeDocumentation/ arch/ | +18 | 0 replies | |
| 2/2 | x86/oprofile: add module parameter option to force a core 2 cpuDocumentation/ arch/ | +16 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] oprofile: introduce module parameter oprofile.cpu_type
The current userland does not yet fully support all cpu types implemented in the kernel. With the module parameter oprofile.cpu_type a certain cpu type can be reported to the oprofile userland and thus makes the kernel usable with current distros.
The event table may not match fully, so care must be taken when using this parameter.
See also this description:
oprofile.cpu_type= Force an oprofile cpu type
This might be useful if you have an older oprofile userland or if you want common events.
Format: { archperfmon | core_2 }
archperfmon: [X86] Force use of architectural
perfmon on Intel CPUs instead of the CPU specific event set.
core_2: [X86] On Intel systems: report core_2 CPU.
Together with Andi's patches the patch set is also in this tree:
git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git fixes
The fixes are intended for v2.6.30.
Andi, please let me now if this works for you and if things can go upstream this way.
-Robert