From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jean Pihet <jean.pihet@newoldbits.com>
Cc: Kevin Hilman <khilman@ti.com>,
Venkatesh Pallipadi <venki@google.com>,
markgross@thegnar.org, linux-kernel@vger.kernel.org,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
"Pihet-XID, Jean" <j-pihet@ti.com>
Subject: Re: [PATCH] CPU C-state breakage with PM Qos change
Date: Mon, 6 Feb 2012 21:16:16 +0100 [thread overview]
Message-ID: <201202062116.16744.rjw@sisk.pl> (raw)
In-Reply-To: <CAORVsuW7mBCZdGqScX5jjaYDhijZH_H7vDKkJ4v6WWHn9rUsGw@mail.gmail.com>
On Monday, February 06, 2012, Jean Pihet wrote:
> Rafael,
>
> On Mon, Feb 6, 2012 at 11:18 AM, Jean Pihet <jean.pihet@newoldbits.com> wrote:
> > Hi Rafael, Mark,
> >
> > On Sun, Feb 5, 2012 at 12:04 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> ...
>
> >> In kernel/power/Makefile:
> >>
> >> obj-$(CONFIG_PM) += main.o qos.o
> >>
> >> I guess that explains things. :-)
> > Initially I thought we should have a way of disabling the feature on
> > some (minimal) kernels and so thought CONFIG_PM was the option to use.
> >
> >> It's quite easy to make qos.o be independent of CONFIG_PM, in which case the
> >> code added by Venki can be removed, so patches welcome (for 3.4, though).
> > I am working on it, more to come soon.
>
> I have a couple of patches ready, to be applied on 3.3-rc1 (so without
> Venki's patch applied).
> The first one is on PM QoS, the second one on per-device PM QoS. Is
> the latter needed?
I'm not sure without looking. :-)
Thanks,
Rafael
WARNING: multiple messages have this Message-ID (diff)
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jean Pihet <jean.pihet@newoldbits.com>
Cc: markgross@thegnar.org, Kevin Hilman <khilman@ti.com>,
Venkatesh Pallipadi <venki@google.com>,
linux-kernel@vger.kernel.org,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
"Pihet-XID, Jean" <j-pihet@ti.com>
Subject: Re: [linux-pm] [PATCH] CPU C-state breakage with PM Qos change
Date: Mon, 6 Feb 2012 21:16:16 +0100 [thread overview]
Message-ID: <201202062116.16744.rjw@sisk.pl> (raw)
In-Reply-To: <CAORVsuW7mBCZdGqScX5jjaYDhijZH_H7vDKkJ4v6WWHn9rUsGw@mail.gmail.com>
On Monday, February 06, 2012, Jean Pihet wrote:
> Rafael,
>
> On Mon, Feb 6, 2012 at 11:18 AM, Jean Pihet <jean.pihet@newoldbits.com> wrote:
> > Hi Rafael, Mark,
> >
> > On Sun, Feb 5, 2012 at 12:04 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> ...
>
> >> In kernel/power/Makefile:
> >>
> >> obj-$(CONFIG_PM) += main.o qos.o
> >>
> >> I guess that explains things. :-)
> > Initially I thought we should have a way of disabling the feature on
> > some (minimal) kernels and so thought CONFIG_PM was the option to use.
> >
> >> It's quite easy to make qos.o be independent of CONFIG_PM, in which case the
> >> code added by Venki can be removed, so patches welcome (for 3.4, though).
> > I am working on it, more to come soon.
>
> I have a couple of patches ready, to be applied on 3.3-rc1 (so without
> Venki's patch applied).
> The first one is on PM QoS, the second one on per-device PM QoS. Is
> the latter needed?
I'm not sure without looking. :-)
Thanks,
Rafael
next prev parent reply other threads:[~2012-02-06 20:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 23:57 [PATCH] CPU C-state breakage with PM Qos change Venkatesh Pallipadi
2012-02-03 0:14 ` Venkatesh Pallipadi
2012-02-03 14:04 ` Pihet-XID, Jean
2012-02-03 14:04 ` Pihet-XID, Jean
2012-02-03 20:02 ` Rafael J. Wysocki
2012-02-03 20:02 ` Rafael J. Wysocki
2012-02-05 3:50 ` mark gross
2012-02-05 3:50 ` mark gross
2012-02-05 11:04 ` Rafael J. Wysocki
2012-02-06 10:18 ` Jean Pihet
2012-02-06 10:18 ` [linux-pm] " Jean Pihet
2012-02-06 16:42 ` Jean Pihet
2012-02-06 16:42 ` [linux-pm] " Jean Pihet
2012-02-06 20:16 ` Rafael J. Wysocki [this message]
2012-02-06 20:16 ` Rafael J. Wysocki
2012-02-07 8:39 ` Jean Pihet
2012-02-07 8:39 ` [linux-pm] " Jean Pihet
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=201202062116.16744.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=khilman@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=markgross@thegnar.org \
--cc=venki@google.com \
/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.