From: Huang Rui <ray.huang@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@suse.de>,
"Peter Zijlstra" <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
"Andy Lutomirski" <luto@amacapital.net>,
Robert Richter <rric@kernel.org>,
"Jacob Shin" <jacob.w.shin@gmail.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Kan Liang <kan.liang@intel.com>, <linux-kernel@vger.kernel.org>,
<spg_linux_kernel@amd.com>, <x86@kernel.org>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>,
Fengguang Wu <fengguang.wu@intel.com>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v5] perf/x86/amd/power: Add AMD accumulated power reporting mechanism
Date: Mon, 29 Feb 2016 23:40:49 +0800 [thread overview]
Message-ID: <20160229154048.GA20610@hr-amur2> (raw)
In-Reply-To: <20160226102952.GD28911@pd.tnic>
On Fri, Feb 26, 2016 at 11:29:52AM +0100, Borislav Petkov wrote:
> On Fri, Feb 26, 2016 at 11:18:28AM +0100, Thomas Gleixner wrote:
> > On Fri, 26 Feb 2016, Huang Rui wrote:
> > > +/* Event code: LSB 8 bits, passed in attr->config any other bit is reserved. */
> > > +#define AMD_POWER_EVENT_MASK 0xFFULL
> > > +
> > > +#define MAX_CUS 8
> >
> > What's that define for? Max compute units? So is that stuff eternaly limited
> > to 8?
>
> I already sent him a cleaned up version with that dumbness removed:
>
> https://lkml.kernel.org/r/20160128145436.GE14274@pd.tnic
>
> Rui, what's up?
>
Sorry, I will remove superfluous MAX_CUS check at next version.
Thanks,
Rui
next prev parent reply other threads:[~2016-02-29 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 9:40 [PATCH v5] perf/x86/amd/power: Add AMD accumulated power reporting mechanism Huang Rui
2016-02-26 10:18 ` Thomas Gleixner
2016-02-26 10:29 ` Borislav Petkov
2016-02-29 15:40 ` Huang Rui [this message]
2016-02-29 18:00 ` Huang Rui
2016-02-29 11:30 ` Thomas Gleixner
2016-03-01 13:58 ` Borislav Petkov
2016-03-02 2:26 ` Huang Rui
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=20160229154048.GA20610@hr-amur2 \
--to=ray.huang@amd.com \
--cc=Aravind.Gopalakrishnan@amd.com \
--cc=acme@kernel.org \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=fengguang.wu@intel.com \
--cc=jacob.w.shin@gmail.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rric@kernel.org \
--cc=spg_linux_kernel@amd.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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