mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Brownell <david-b@pacbell.net>,
	Michal Piotrowski <michal.k.k.piotrowski@gmail.com>,
	linux-usb-devel@lists.sourceforge.net, Greg KH <gregkh@suse.de>,
	LKML <linux-kernel@vger.kernel.org>,
	"Stuart_Hayes@Dell.com" <Stuart_Hayes@dell.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Daniel Exner <dex@dragonslave.de>
Subject: Re: [linux-usb-devel] [4/4] 2.6.23-rc3: known regressions
Date: Mon, 20 Aug 2007 23:04:14 -0700	[thread overview]
Message-ID: <1187676254.2676.6.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1187675488.2676.3.camel@laptopd505.fenrus.org>


On Mon, 2007-08-20 at 22:51 -0700, Arjan van de Ven wrote:
> and the C-state code will honor it. CPUFREQ doesn't honor it yet but
> that's easy to add..

untested patch to add this to cpufreq; this is probably a good idea in
general even if using the latency framework doesn't end up being used
for fixing this regression...


--- linux-2.6.23-rc2/drivers/cpufreq/cpufreq.c.org	2007-08-20 22:58:32.000000000 -0700
+++ linux-2.6.23-rc2/drivers/cpufreq/cpufreq.c	2007-08-20 23:02:21.000000000 -0700
@@ -1604,6 +1604,12 @@ static int __cpufreq_set_policy(struct c
 	if (ret)
 		goto error_out;
 
+
+	if (system_latency_constraint() < policy->cpuinfo.transition_latency) {
+		ret = -EINVAL;
+		goto error_out;
+	}
+
 	/* notification of the new policy */
 	blocking_notifier_call_chain(&cpufreq_policy_notifier_list,
 			CPUFREQ_NOTIFY, policy);



  reply	other threads:[~2007-08-21  6:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <46C098FD.1030601@googlemail.com>
2007-08-13 17:59 ` [2/4] " Michal Piotrowski
2007-08-13 23:29   ` Luca Tettamanti
2007-08-14  6:37     ` Michal Piotrowski
2007-08-13 17:59 ` [3/4] " Michal Piotrowski
2007-08-14 22:09   ` Francois Romieu
2007-08-13 17:59 ` [4/4] " Michal Piotrowski
2007-08-21  1:41   ` [linux-usb-devel] " David Brownell
2007-08-21  2:02     ` Linus Torvalds
2007-08-21  4:02       ` David Brownell
2007-08-21  4:15         ` Linus Torvalds
2007-08-21  4:48           ` David Brownell
2007-08-21  5:31             ` Linus Torvalds
2007-08-21  5:51               ` Arjan van de Ven
2007-08-21  6:04                 ` Arjan van de Ven [this message]
2007-08-21  6:26                   ` Linus Torvalds
2007-08-21  6:28                     ` Arjan van de Ven
2007-08-21  6:45                       ` Linus Torvalds
2007-08-21  6:25                 ` Linus Torvalds
2007-08-21  6:24                   ` Arjan van de Ven
2007-08-21  6:03               ` Linus Torvalds
2007-08-21  6:34                 ` David Brownell
2007-08-21  6:52                   ` Linus Torvalds
2007-08-21  7:24                     ` Linus Torvalds
2007-08-22  3:34                       ` Linus Torvalds
2007-08-22 14:42                         ` Stuart_Hayes
2007-08-22 18:41                           ` Linus Torvalds
2007-08-22 20:41                             ` Stuart_Hayes
2007-08-22 23:35                         ` Junio C Hamano
2007-08-21  4:27       ` [linux-usb-devel] " David Brownell

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=1187676254.2676.6.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=Stuart_Hayes@dell.com \
    --cc=akpm@linux-foundation.org \
    --cc=david-b@pacbell.net \
    --cc=dex@dragonslave.de \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=michal.k.k.piotrowski@gmail.com \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®