Re: [PATCH 0/2] oprofile: introduce module parameter oprofile.cpu_type

[Andi Kleen]

On Wed, May 06, 2009 at 02:39:12PM +0200, Robert Richter wrote:
> 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.

On Intel systems forcing archperfmon is the only one that makes sense
nd only if the CPU supports arch perfmon(btw that's already in my patchkit
which you haven't commented on so far)

I don't thinking forcing core2 on a system like Nehalem with completely
different events is a good idea though. This just means if the user
selects anything unusual they will get junk data, which is just
a bad design.

Also if you force core2 on a P4 system the kernel will just oops
because it will access MSRs that are not there. So I don't think
that's a good idea.

It means you have to update oprofile userland at least once until
you have arch perfmon support, but I think even Linus will be able
to do that :) Hopefully Maynard will do a new release soon.

The force of core2 is nacked from my side.

-Andi

-- 
ak@xxxxxxxxxxxxxxx -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/