public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: mark gross <640e9920@gmail.com>
To: markgross@thegnar.org
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	Linux PM <linux-pm@lists.linux-foundation.org>
Subject: Re: [RFC] pm_qos: reimplement using plists
Date: Tue, 8 Jun 2010 06:31:57 -0700	[thread overview]
Message-ID: <20100608133157.GA26668@gvim.org> (raw)
In-Reply-To: <20100606213954.GD8610@gvim.org>

On Sun, Jun 06, 2010 at 02:39:54PM -0700, mark gross wrote:
> On Sat, Jun 05, 2010 at 12:58:08PM -0500, James Bottomley wrote:
> > A lot of the pm_qos extremal value handling is really duplicating what a
> > priority ordered list does, just in a less efficient fashion.  Simply
> > redoing the implementation in terms of a plist gets rid of a lot of this
> > junk (although there are several other strange things that could do with
> > tidying up, like pm_qos_request_list has to carry the pm_qos_class with
> > every node, simply because it doesn't get passed in to
> > pm_qos_update_request even though every caller knows full well what
> > parameter it's updating).
> > 
> > I think this redo is a win independent of android, so we should do
> > something like this now.
> > 
> > There is one nasty that should probably be fixed in plists not open
> > coded here: plist_first gives the highest priority value, but there's no
> > corresponding API to give the lowest (even though you can get it from
> > the head.nodes_list.prev) ... if the sched people are OK, I'll correct
> > this with the final patch set.
> > 
> > James
> > 
> > ---
> > 
> >  kernel/pm_qos_params.c |  152 +++++++++++++++++++++++-------------------------
> >  1 files changed, 73 insertions(+), 79 deletions(-)
> > 
> > diff --git a/kernel/pm_qos_params.c b/kernel/pm_qos_params.c
> > index f42d3f7..241fa79 100644
> > --- a/kernel/pm_qos_params.c
> > +++ b/kernel/pm_qos_params.c
> > @@ -30,6 +30,7 @@
> >  /*#define DEBUG*/

snip

> > @@ -251,22 +244,27 @@ void pm_qos_update_request(struct pm_qos_request_list *pm_qos_req,
> >  	unsigned long flags;
> >  	int pending_update = 0;
> >  	s32 temp;
> > +	struct pm_qos_object *o;
> >  
> > -	if (pm_qos_req) { /*guard against callers passing in null */
> > -		spin_lock_irqsave(&pm_qos_lock, flags);
> > -		if (new_value == PM_QOS_DEFAULT_VALUE)
> > -			temp = pm_qos_array[pm_qos_req->pm_qos_class]->default_value;
> > -		else
> > -			temp = new_value;
> > +	if (!pm_qos_req) /*guard against callers passing in null */
> > +		return;
> 
> need a better test to see if the pm_qos_req is in the plist or not as we
> move to a caller allocated design.
>

snip  
> >  void pm_qos_remove_request(struct pm_qos_request_list *pm_qos_req)
> >  {
> > -	unsigned long flags;
> > -	int qos_class;
> > +	struct pm_qos_object *o;
> >  
> >  	if (pm_qos_req == NULL)
> >  		return;
> >  		/* silent return to keep pcm code cleaner */
> 
> need a way to tell if the request is in the list or not so we don't
> crater removing a plist node that isn't in the list.
> 
snip
>

I found that e1000e will panic on rmmod because of it attempting to
removing of a pm_qos request that it never added.

This is an ugly patch, but I think its needed for a while to clean out
the abusers, then it can be updated to not be so noisy.


--mgross

--Signed-off-by: mark gross <markgross@thegnar.org>



>From fb713f95b83ea3744c31917cfd019bf3e32349b3 Mon Sep 17 00:00:00 2001
From: markgross <markgross@thegnar.org>
Date: Tue, 8 Jun 2010 06:22:01 -0700
Subject: [PATCH] check and complain about abuse of the api to avoid panics

---
 kernel/pm_qos_params.c |   12 +++++++++++-
 1 files changed, 11 insertions(+), 1 deletions(-)

diff --git a/kernel/pm_qos_params.c b/kernel/pm_qos_params.c
index f1d3d23..4bded27 100644
--- a/kernel/pm_qos_params.c
+++ b/kernel/pm_qos_params.c
@@ -212,7 +212,7 @@ void pm_qos_add_request(struct pm_qos_request_list *dep,
 	int new_value;
 
 	if (pm_qos_request_active(dep))
-		return;
+		return; /* already in the list */
 
 	if (value == PM_QOS_DEFAULT_VALUE)
 		new_value = o->default_value;
@@ -244,6 +244,11 @@ void pm_qos_update_request(struct pm_qos_request_list *pm_qos_req,
 
 	if (!pm_qos_req) /*guard against callers passing in null */
 		return;
+	if (!pm_qos_request_active(pm_qos_req)) {
+		WARN(true, "pm_qos: update to an unregistered request");
+		dump_stack();
+		return;
+	}
 
 	o = pm_qos_array[pm_qos_req->pm_qos_class];
 
@@ -279,6 +284,11 @@ void pm_qos_remove_request(struct pm_qos_request_list *pm_qos_req)
 	if (pm_qos_req == NULL)
 		return;
 		/* silent return to keep pcm code cleaner */
+	if (!pm_qos_request_active(pm_qos_req)) {
+		WARN(true, "pm_qos: removal an unregistered request");
+		dump_stack();
+		return;
+	}
 
 	o = pm_qos_array[pm_qos_req->pm_qos_class];
 	update_target(o, &pm_qos_req->list, 1);
-- 
1.6.3.3



 

  parent reply	other threads:[~2010-06-08 13:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-05 17:58 [RFC] pm_qos: reimplement using plists James Bottomley
2010-06-05 18:17 ` Rafael J. Wysocki
2010-06-05 18:19   ` James Bottomley
2010-06-06 21:05 ` mark gross
2010-06-07  2:41   ` James Bottomley
2010-06-06 21:39 ` mark gross
2010-06-07  3:05   ` James Bottomley
2010-06-09  6:38     ` Florian Mickler
2010-06-09 14:03       ` James Bottomley
2010-06-08 13:31   ` mark gross [this message]
2010-06-08 15:52     ` James Bottomley
2010-06-09  2:42       ` mark gross
2010-06-09 14:03         ` James Bottomley

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=20100608133157.GA26668@gvim.org \
    --to=640e9920@gmail.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=markgross@thegnar.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