cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 64261] New: Intel Pstate driver truncates to pstate instead of rounding to nearest pstate
Date: Sat, 02 Nov 2013 21:52:12 +0000	[thread overview]
Message-ID: <bug-64261-12968@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=64261

            Bug ID: 64261
           Summary: Intel Pstate driver truncates to pstate instead of
                    rounding to nearest pstate
           Product: Power Management
           Version: 2.5
    Kernel Version: 3.12rc7
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: cpufreq
          Assignee: cpufreq@vger.kernel.org
          Reporter: dsmythies@telus.net
        Regression: No

Created attachment 113151
  --> https://bugzilla.kernel.org/attachment.cgi?id=113151&action=edit
shows rounded pstate and current actual for frequency Vs. requested.

The Intel Pstate driver seems to truncate its calculations to the lower integer
pstate. The suggestion is that it should round to the nearest pstate. Recent
(kernel 3.12RC7) math improvements have made achieving 100% frequency better,
but rounding would make it more robust.

The attachment demonstrates.

-- 
You are receiving this mail because:
You are the assignee for the bug.

             reply	other threads:[~2013-11-02 21:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-02 21:52 bugzilla-daemon [this message]
2013-11-04  7:17 ` [Bug 64261] Intel Pstate driver truncates to pstate instead of rounding to nearest pstate bugzilla-daemon
2013-11-04 16:14 ` bugzilla-daemon
2013-11-04 16:54 ` bugzilla-daemon
2013-11-04 18:39 ` bugzilla-daemon
2013-11-04 22:19 ` bugzilla-daemon
2013-11-05  1:28 ` bugzilla-daemon
2013-11-05  7:21 ` bugzilla-daemon
2013-11-05  7:35 ` bugzilla-daemon
2013-11-05  8:12 ` bugzilla-daemon
2013-11-05 15:06 ` bugzilla-daemon
2013-11-06  5:34 ` bugzilla-daemon
2013-11-06  5:38 ` bugzilla-daemon
2013-11-06  5:43 ` bugzilla-daemon
2013-11-06  5:48 ` bugzilla-daemon
2013-11-06  6:04 ` bugzilla-daemon
2013-11-06 18:58 ` bugzilla-daemon
2013-11-06 19:44 ` bugzilla-daemon
2014-04-18  3:02 ` bugzilla-daemon

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=bug-64261-12968@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=cpufreq@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).