public inbox for cpufreq@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: cpufreq@vger.kernel.org
Subject: [Bug 60839] scaling_max_freq cannot be set to values larger than bios_limit
Date: Tue, 10 Sep 2013 13:15:48 +0000	[thread overview]
Message-ID: <bug-60839-12968-s9KmFEVM8p@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60839-12968@https.bugzilla.kernel.org/>

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

--- Comment #4 from Sven Köhler <sven.koehler@gmail.com> ---
(In reply to Lan Tianyu from comment #3)
> > b) userspace should never be able to set scaling_max_freq to a value larger
> > than bios_limit
> 
> Actually, you can set the value larger than bios_limit and it will works
> when bios_limit raises.

That is exactly what didn't work! A write to the scaling_max_freq via sysfs was
clipped by bios_limit, as far as I can tell. It never want up again, after a
write to scaling_max_freq occured. I reproduced this having a small while loop
in the bash shell, that wrote the maximum CPU frequency to scaling_max_freq
while bios_limit was low.

I will try to reproduce the issue again and post the bash loop code here.

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

  parent reply	other threads:[~2013-09-10 13:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 12:47 [Bug 60839] New: scaling_max_freq cannot be set to values larger than bios_limit bugzilla-daemon
2013-09-10  8:28 ` [Bug 60839] " bugzilla-daemon
2013-09-10  8:36 ` bugzilla-daemon
2013-09-10  9:46 ` bugzilla-daemon
2013-09-10 12:45 ` bugzilla-daemon
2013-09-10 13:15 ` bugzilla-daemon [this message]
2013-09-10 14:19 ` bugzilla-daemon
2013-09-11 19:49 ` bugzilla-daemon
2013-09-12 14:07 ` bugzilla-daemon
2013-09-12 14:49 ` bugzilla-daemon
2013-09-18  3:27 ` bugzilla-daemon
2013-10-14  7:58 ` 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-60839-12968-s9KmFEVM8p@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