From: Robert Richter <robert.richter@amd.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org,
oprofile-list@lists.sourceforge.net,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] oprofile: document undocumented oprofile.p4force argument
Date: Thu, 25 Sep 2008 22:10:45 +0200 [thread overview]
Message-ID: <20080925201045.GK23557@erda.amd.com> (raw)
In-Reply-To: <1219250433-25516-5-git-send-email-andi@firstfloor.org>
On 20.08.08 18:40:33, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> It's actually useless now, but document it anyways.
We should rework/remove this (maybe later), if it makes no longer
sense to keep it. If we had have a force_cpu_type implementation this
could be thrown away.
But as long as it is in it's better to have it documented.
-Robert
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> ---
> Documentation/kernel-parameters.txt | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index 10c8b1b..5e77e1a 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -1491,6 +1491,12 @@ and is between 256 and 4096 characters. It is defined in the file
> in oprofile on Intel CPUs. The kernel selects the
> correct default on its own.
>
> + oprofile.p4force=1 [X86]
> + On Intel NetBurst CPUs assume new models are compatible
> + to older ones. This might allow oprofile to be used when
> + the kernel doesn't know the CPU, but is slightly dangerous.
> + Should be obsolete by now.
> +
> osst= [HW,SCSI] SCSI Tape Driver
> Format: <buffer_size>,<write_threshold>
> See also Documentation/scsi/st.txt.
> --
> 1.5.6
>
>
--
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com
next prev parent reply other threads:[~2008-09-25 20:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 16:40 oprofile: Implement Intel architectural perfmon Andi Kleen
2008-08-20 16:40 ` [PATCH] oprofile: drop const in num counters field Andi Kleen
2008-08-20 16:40 ` [PATCH] oprofile: Implement Intel architectural perfmon support Andi Kleen
2008-08-20 16:40 ` [PATCH] oprofile: Don't report Nehalem as core_2 Andi Kleen
2008-08-20 16:40 ` [PATCH] oprofile: document undocumented oprofile.p4force argument Andi Kleen
2008-09-25 20:10 ` Robert Richter [this message]
2008-09-25 20:05 ` [PATCH] oprofile: Don't report Nehalem as core_2 Robert Richter
2008-09-25 20:00 ` [PATCH] oprofile: Implement Intel architectural perfmon support Robert Richter
2008-09-26 0:44 ` Andi Kleen
2008-09-26 3:23 ` Robert Richter
2008-09-26 23:09 ` Andi Kleen
2008-09-28 7:33 ` Robert Richter
2008-09-25 19:32 ` oprofile: Implement Intel architectural perfmon 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=20080925201045.GK23557@erda.amd.com \
--to=robert.richter@amd.com \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.