From: Andi Kleen <ak@linux.intel.com>
To: Robert Richter <robert.richter@amd.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org,
oprofile-list@lists.sourceforge.net
Subject: Re: [PATCH] oprofile: Implement Intel architectural perfmon support
Date: Fri, 26 Sep 2008 16:09:02 -0700 [thread overview]
Message-ID: <48DD6B8E.5050106@linux.intel.com> (raw)
In-Reply-To: <20080926032328.GN23557@erda.amd.com>
Robert Richter wrote:
> I think this would be the best solution, providing a parameter
>
> oprofile.force_pmu=<oprofile arch string>
>
> This can easily be implemented and also reused by others. I would be
> fine with this solution. No separate patch needed then.
Ok I can implement that, but it'll be a separate patch. Might be until
next week that I can work on it though.
-Andi
next prev parent reply other threads:[~2008-09-26 23:08 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
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 [this message]
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=48DD6B8E.5050106@linux.intel.com \
--to=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sourceforge.net \
--cc=robert.richter@amd.com \
/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