linux-kernel - [PATCH 0/2] oprofile: introduce module parameter oprofile.cpu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <1241613554-31539-1-git-send-email-robert.richter@amd.com>
Date:	Wed, 6 May 2009 14:39:12 +0200
From:	Robert Richter <robert.richter@....com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	LKML <linux-kernel@...r.kernel.org>,
	oprofile-list <oprofile-list@...ts.sourceforge.net>
Subject: [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

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