On Thu, Mar 31, 2016 at 1:25 AM, Sedat Dilek <sedat.di...@gmail.com> wrote: > On Thu, Mar 31, 2016 at 1:17 AM, Pandruvada, Srinivas > <srinivas.pandruv...@intel.com> wrote: >> On Wed, 2016-03-30 at 15:46 -0700, Srinivas Pandruvada wrote: >>> On Thu, 2016-03-31 at 00:25 +0200, Rafael J. Wysocki wrote: >>> > >>> > On 3/31/2016 12:18 AM, Srinivas Pandruvada wrote: >>> > > >>> > > >>> > > On Wed, 2016-03-30 at 23:41 +0200, Sedat Dilek wrote: >>> > > > >>> > > > >>> > > > Hi, >>> > > > >>> > > > I am using Intel-PState-Driver here with v4.6-rc1 and Intel- >>> > > > SandyBridge-CPU. >>> > > > >>> > > > Here are my turbostat results attached. >>> > > > >>> > > > $ cd $BUILD_DIR >>> > > > $ LC_ALL=C make -C tools/ turbostat >>> > > > >>> > > > $ sudo ./turbostat -i 1 --msr=0x199 --debug --out >>> > > > /tmp/turbostat-i-1-msr-0x199-debug.txt >>> > > > >>> > > > Will try <https://patchwork.kernel.org/patch/8702071/>. >>> > > > >>> > > > Please see attached files. >>> > > > >>> > > Thanks. Your logs make sense. You have config set to performance >>> > > mode >>> > > by default (Which I believe default in all kernel Ubuntu). So as >>> > > expected Intel P state was asking for max. So there is no issue >>> > > here. >>> > But the behavior is different from what it used to be, isn't it? >>> >
[cut] > > Too much questions. OK > I switched to CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE=y and tested with > the simplified revert-patch of Rafael. Why do you need the revert patch in the first place?
