[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1701241409270.3301@vshiva-Udesk>
Date: Tue, 24 Jan 2017 14:10:33 -0800 (PST)
From: Shivappa Vikas <vikas.shivappa@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>
cc: Shivappa Vikas <vikas.shivappa@...el.com>,
Vikas Shivappa <vikas.shivappa@...ux.intel.com>,
linux-kernel@...r.kernel.org, x86@...nel.org, hpa@...or.com,
mingo@...nel.org, peterz@...radead.org, ravi.v.shankar@...el.com,
tony.luck@...el.com, fenghua.yu@...el.com, h.peter.anvin@...el.com
Subject: Re: [PATCH 1/8] Documentation, x86: Documentation for Intel Mem b/w
allocation user interface
On Mon, 23 Jan 2017, Thomas Gleixner wrote:
> On Mon, 23 Jan 2017, Shivappa Vikas wrote:
>> On Wed, 18 Jan 2017, Thomas Gleixner wrote:
>>> If it's going to stay, then Intel should be able to provide simple tables
>>> which give us the required information for a particular CPU model.
>>
>> By sample table - does this mean we can map a throttle value in non-linear
>> scale to its percentage ?
>
> Exactly. And that map should be provided by Intel simply because it's a
> royal pain in the neck if users have to map random power of 2 values to
> something useful. And of course every user has to do the same thing on
> their own. That'd be more than silly.
Ok. Right now we dont have this capability on any SKUs, so i will just do a call
to say get_throttle_map() for non_linear scale and fail if there is a nonlinear
scale and later we can update to API to actually return the map for SKUs that
support it.
Thanks,
Vikas
>
> Thanks,
>
> tglx
>
>
>
>
Powered by blists - more mailing lists