From: Robert Richter <robert.richter@amd.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jason Yeh <jason.yeh@amd.com>,
Thomas Gleixner <tglx@linutronix.de>,
oprofile-list <oprofile-list@lists.sourceforge.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Oprofile Multiplexing Patch
Date: Tue, 29 Jul 2008 19:54:07 +0200 [thread overview]
Message-ID: <20080729175407.GA30245@erda.amd.com> (raw)
In-Reply-To: <20080726111626.GL25890@elte.hu>
On 26.07.08 13:16:26, Ingo Molnar wrote:
>
> > From: Jason Yeh <jason.yeh@amd.com>
>
> > diff --git a/arch/x86/oprofile/op_model_p4.c b/arch/x86/oprofile/op_model_p4.c
> > index 56b4757..e641545 100644
> > --- a/arch/x86/oprofile/op_model_p4.c
> > +++ b/arch/x86/oprofile/op_model_p4.c
> > @@ -701,6 +701,8 @@ static void p4_shutdown(struct op_msrs const * const msrs)
> > struct op_x86_model_spec const op_p4_ht2_spec = {
> > .num_counters = NUM_COUNTERS_HT2,
> > .num_controls = NUM_CONTROLS_HT2,
> > + .num_hardware_counters = NUM_COUNTERS_HT2,
> > + .num_hardware_controls = NUM_CONTROLS_HT2,
>
> is there any further change needed for Intel CPUs to benefit from
> multiplexing too, up to the max of 32 controls? (AFAICS it should work
> as-is, correct?)
I would like to wait with this change until the code base is
stable. There could be some follow-up changes that would require more
rework then.
-Robert
>
> Ingo
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com
prev parent reply other threads:[~2008-07-29 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 21:05 [PATCH] Oprofile Multiplexing Patch Robert Richter
2008-07-26 11:16 ` Ingo Molnar
2008-07-29 17:54 ` Robert Richter [this message]
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=20080729175407.GA30245@erda.amd.com \
--to=robert.richter@amd.com \
--cc=jason.yeh@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oprofile-list@lists.sourceforge.net \
--cc=tglx@linutronix.de \
/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