From: Jean Pihet <jean.pihet@newoldbits.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>,
Venkatesh Pallipadi <venki@google.com>
Cc: Kevin Hilman <khilman@ti.com>,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>,
"Pihet-XID, Jean" <j-pihet@ti.com>,
linux-kernel@vger.kernel.org, markgross@thegnar.org
Subject: Re: [PATCH] CPU C-state breakage with PM Qos change
Date: Tue, 7 Feb 2012 09:39:19 +0100 [thread overview]
Message-ID: <CAORVsuWgAgxgJ2ej0psZb1OKN8SE39PF2URdikWzVHJzUMKQMA@mail.gmail.com> (raw)
In-Reply-To: <201202062116.16744.rjw@sisk.pl>
On Mon, Feb 6, 2012 at 9:16 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> 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. :-)
That makes sense ;p
Just sent out the patch set as '[PATCH 0/2] PM / QoS: unconditionally
build the feature'.
It has been compile tested only using the i386 defconfig, with and
without CONFIG_PM.
It requires some more testing on x86.
Venki, can you check it out if this fixes the initial problem?
>
> Thanks,
> Rafael
Regards,
Jean
prev parent reply other threads:[~2012-02-07 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1328227065-22045-1-git-send-email-venki@google.com>
[not found] ` <1328228079-20716-1-git-send-email-venki@google.com>
2012-02-03 14:04 ` [PATCH] CPU C-state breakage with PM Qos change Pihet-XID, Jean
2012-02-03 20:02 ` Rafael J. Wysocki
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 16:42 ` Jean Pihet
2012-02-06 20:16 ` Rafael J. Wysocki
2012-02-07 8:39 ` Jean Pihet [this message]
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=CAORVsuWgAgxgJ2ej0psZb1OKN8SE39PF2URdikWzVHJzUMKQMA@mail.gmail.com \
--to=jean.pihet@newoldbits.com \
--cc=j-pihet@ti.com \
--cc=khilman@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=markgross@thegnar.org \
--cc=rjw@sisk.pl \
--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 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 NNTP newsgroup(s).