From: Robert Richter <robert.richter@amd.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
oprofile-list <oprofile-list@lists.sourceforge.net>
Subject: [PATCH 0/2] oprofile: introduce module parameter oprofile.cpu_type
Date: Wed, 6 May 2009 14:39:12 +0200 [thread overview]
Message-ID: <1241613554-31539-1-git-send-email-robert.richter@amd.com> (raw)
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
next reply other threads:[~2009-05-06 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 12:39 Robert Richter [this message]
2009-05-06 12:39 ` [PATCH 1/2] oprofile: introduce module_param oprofile.cpu_type Robert Richter
2009-05-06 12:39 ` [PATCH 2/2] x86/oprofile: add module parameter option to force a core 2 cpu Robert Richter
2009-05-06 14:47 ` [PATCH 0/2] oprofile: introduce module parameter oprofile.cpu_type Andi Kleen
2009-05-06 16:39 ` Robert Richter
2009-06-10 13:07 ` Robert Richter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1241613554-31539-1-git-send-email-robert.richter@amd.com \
--to=robert.richter@amd.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oprofile-list@lists.sourceforge.net \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox