All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Gmeiner <christian.gmeiner@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] x86: queensbay: switche P state to the highest freq
Date: Tue, 10 Apr 2018 11:48:29 +0200	[thread overview]
Message-ID: <CAH9NwWfUO9YhEKjVd6d195mSbkwbuVwuwUD_offOaVrfGmmtrQ@mail.gmail.com> (raw)
In-Reply-To: <CAEUhbmUACE0v9d8-9Xrjs6vmPvXx0Xj_gLs_=tZotTpda7DpuA@mail.gmail.com>

2018-04-10 11:11 GMT+02:00 Bin Meng <bmeng.cn@gmail.com>:
> Hi Christian,
>
> On Tue, Apr 10, 2018 at 5:09 PM, Christian Gmeiner
> <christian.gmeiner@gmail.com> wrote:
>> Hi Bin,
>>
>> 2018-04-10 11:07 GMT+02:00 Bin Meng <bmeng.cn@gmail.com>:
>>> Hi Christian,
>>>
>>> On Tue, Apr 10, 2018 at 4:47 PM, Christian Gmeiner
>>> <christian.gmeiner@gmail.com> wrote:
>>>> Hi Bin
>>>>
>>>> Thanks for you quick review!
>>>>
>>>>>
>>>>> On Tue, Apr 10, 2018 at 4:01 PM, Christian Gmeiner
>>>>> <christian.gmeiner@gmail.com> wrote:
>>>>>> Fixes performance issue when running vx5/vx7 images.
>>>>>
>>>>> Could you elaborate more on what performance issue you are seeing?
>>>>>
>>>>
>>>> The cache performance was bad without this change. We found this problem
>>>> when switching from bldk to u-boot.
>>>>
>>>> old: https://imagebin.ca/v/3xssw7stbY6A
>>>> new: https://imagebin.ca/v/3xstHMCC9fmJ
>>>
>>> Thank you for the benchmark data. Then please consider describing your
>>> benchmark test suite and on what configuration the data is worse
>>> without this patch (eg: sequential 128-bit read) in the commit
>>> message. This will help other people understand the patch and the
>>> commit in the future.
>>>
>>
>> Will do.
>>
>>>>
>>>>> nits: better to spell out "VxWorks"
>>>>
>>>> ok
>>>>
>>>>>
>>>>>>
>>>>>> Signed-off-by: Christian Gmeiner <christian.gmeiner@gmail.com>
>>>>>> ---
>>>>>>  arch/x86/cpu/queensbay/Makefile |  2 +-
>>>>>>  arch/x86/cpu/queensbay/cpu.c    | 61 +++++++++++++++++++++++++++++++++++++++++
>>>>>>  2 files changed, 62 insertions(+), 1 deletion(-)
>>>>>>  create mode 100644 arch/x86/cpu/queensbay/cpu.c
>>>>>>
>>>>>> diff --git a/arch/x86/cpu/queensbay/Makefile b/arch/x86/cpu/queensbay/Makefile
>>>>>> index c0681995bd..3dd23465d4 100644
>>>>>> --- a/arch/x86/cpu/queensbay/Makefile
>>>>>> +++ b/arch/x86/cpu/queensbay/Makefile
>>>>>> @@ -5,4 +5,4 @@
>>>>>>  #
>>>>>>
>>>>>>  obj-y += fsp_configs.o irq.o
>>>>>> -obj-y += tnc.o
>>>>>> +obj-y += tnc.o cpu.o
>>>>>> diff --git a/arch/x86/cpu/queensbay/cpu.c b/arch/x86/cpu/queensbay/cpu.c
>>>>>> new file mode 100644
>>>>>> index 0000000000..e98e4ac8ef
>>>>>> --- /dev/null
>>>>>> +++ b/arch/x86/cpu/queensbay/cpu.c
>>>>>> @@ -0,0 +1,61 @@
>>>>>> +/*
>>>>>> + * Copyright (C) 2016, Bachmann electronic GmbH
>>>>>
>>>>> nits: 2018?
>>>>>
>>>>
>>>> This change was made some months ago :) But yeah.. can change it.
>>>>
>>>>>> + *
>>>>>> + * SPDX-License-Identifier:    GPL-2.0+
>>>>>> + */
>>>>>> +
>>>>>> +#include <common.h>
>>>>>> +#include <cpu.h>
>>>>>> +#include <dm.h>
>>>>>> +#include <asm/cpu.h>
>>>>>> +#include <asm/cpu_x86.h>
>>>>>> +#include <asm/msr.h>
>>>>>> +
>>>>>> +static void set_max_freq(void)
>>>>>> +{
>>>>>> +       msr_t msr;
>>>>>> +
>>>>>> +       msr = msr_read(MSR_IA32_MISC_ENABLES);
>>>>>> +       msr.lo |= (1 << 16);
>>>>>
>>>>> Please use macro instead of magic numbers
>>>>
>>>> ok
>>>>
>>>>>
>>>>>> +       msr_write(MSR_IA32_MISC_ENABLES, msr);
>>>>>> +
>>>>>> +       msr = msr_read(MSR_IA32_PERF_CTL);
>>>>>> +       msr.lo = 0x101f;
>>>>>
>>>>> ditto
>>>>
>>>> ok

I *think* I have read this msr running under a 'good' bios so I am not
really sure
what the meaning of the bits are. I tried a quick google and did not found any
E6xx datasheet containing the description. Is it okay to just use the
magic value here?

-- 
greets
--
Christian Gmeiner, MSc

https://christian-gmeiner.info

  reply	other threads:[~2018-04-10  9:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-10  8:01 [U-Boot] [PATCH] x86: queensbay: switche P state to the highest freq Christian Gmeiner
2018-04-10  8:17 ` Bin Meng
2018-04-10  8:47   ` Christian Gmeiner
2018-04-10  9:07     ` Bin Meng
2018-04-10  9:09       ` Christian Gmeiner
2018-04-10  9:11         ` Bin Meng
2018-04-10  9:48           ` Christian Gmeiner [this message]
2018-04-10 10:00             ` Bin Meng

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=CAH9NwWfUO9YhEKjVd6d195mSbkwbuVwuwUD_offOaVrfGmmtrQ@mail.gmail.com \
    --to=christian.gmeiner@gmail.com \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.