linux-kernel - Re: [PATCH 01/16] x86/oprofile: add module parameter option to force a core 2 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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 17 Jun 2009 12:57:26 +0200
From:	Robert Richter <robert.richter@....com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	Ingo Molnar <mingo@...e.hu>,
	the arch/x86 maintainers <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 01/16] x86/oprofile: add module parameter option to
	force a core 2 cpu

On 16.06.09 13:15:40, Jeremy Fitzhardinge wrote:
> From: Robert Richter <robert.richter@....com>
> 
> The current userland does not yet fully support all cpu types
> implemented in the kernel. With the module parameter:
> 
>  oprofile.cpu_type=core_2
> 
> the kernel reports a core_2 cpu to the userland on an Intel system and
> thus makes oprofile usable with current distros.
> 
> Cc: Linus Torvalds <torvalds@...ux-foundation.org>
> Cc: Andi Kleen <ak@...ux.intel.com>
> Signed-off-by: Robert Richter <robert.richter@....com>
> ---
>  Documentation/kernel-parameters.txt |    3 ++-
>  arch/x86/oprofile/nmi_int.c         |   17 ++++++++++++++---
>  2 files changed, 16 insertions(+), 4 deletions(-)

Jeremy,

I dropped this patch. See this thread:

 http://lkml.org/lkml/2009/5/6/234

Does your patch series depends on this?

-Robert

-- 
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@....com

--
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/