From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-pm@vger.kernel.org, linaro-kernel@lists.linaro.org,
linux-acpi@vger.kernel.org, Len Brown <len.brown@intel.com>
Subject: Re: [PATCH 1/2] cpuidle: acpi: Remove TIME_INVALID flag from acpi
Date: Thu, 04 Dec 2014 09:53:53 +0100 [thread overview]
Message-ID: <54802121.2030407@linaro.org> (raw)
In-Reply-To: <546F53CF.8070004@linaro.org>
On 11/21/2014 04:01 PM, Daniel Lezcano wrote:
> On 11/21/2014 04:05 PM, Rafael J. Wysocki wrote:
>> On Friday, November 21, 2014 10:29:51 AM Daniel Lezcano wrote:
>>> The commit 8e92b6605d introduced the TIME_VALID flag for the C1 state
>>> if this one is a mwait state assuming the interrupt will be enabled
>>> before reading the end time of the idle state.
>>>
>>> The changelog of this commit mention a potential problem with the menu
>>> governor but not a real observation and I assume it described an old
>>> code as the commit is from 2008.
>>>
>>> I have been digging through the code and I didn't find any place
>>> where the
>>> interrupts are enabled before reading the time. Moreover with the
>>> changes
>>> in the meantime, we moved the time measurements in the cpuidle core
>>> as well
>>> as the interrupts enabling making sure the time is measured before the
>>> interrupt are enabled again in a single place.
>>>
>>> Remove this test as the time measurement is always valid for this
>>> state.
>>>
>>> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
>>
>> Well, I need Len to have a look at this.
Hi,
any news on that ?
Thanks
-- Daniel
> Ok thanks.
>
> If you have time, is it possible also you have a look at the patchset I
> sent :
>
> [PATCH V3 0/6] sched: idle: cpuidle: cleanups and fixes
>
> and give your opinion about the poll state Peter and I we were discussing ?
>
> Regards
>
> -- Daniel
>
>>> ---
>>> drivers/acpi/processor_idle.c | 2 --
>>> 1 file changed, 2 deletions(-)
>>>
>>> diff --git a/drivers/acpi/processor_idle.c
>>> b/drivers/acpi/processor_idle.c
>>> index 380b4b4..7afba40 100644
>>> --- a/drivers/acpi/processor_idle.c
>>> +++ b/drivers/acpi/processor_idle.c
>>> @@ -985,8 +985,6 @@ static int
>>> acpi_processor_setup_cpuidle_states(struct acpi_processor *pr)
>>> state->flags = 0;
>>> switch (cx->type) {
>>> case ACPI_STATE_C1:
>>> - if (cx->entry_method != ACPI_CSTATE_FFH)
>>> - state->flags |= CPUIDLE_FLAG_TIME_INVALID;
>>>
>>> state->enter = acpi_idle_enter_c1;
>>> state->enter_dead = acpi_idle_play_dead;
>>>
>>
>
>
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2014-12-04 8:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 9:29 [PATCH 1/2] cpuidle: acpi: Remove TIME_INVALID flag from acpi Daniel Lezcano
2014-11-21 9:29 ` [PATCH 2/2] cpuidle: Remove TIME_INVALID flag Daniel Lezcano
2014-11-21 15:05 ` [PATCH 1/2] cpuidle: acpi: Remove TIME_INVALID flag from acpi Rafael J. Wysocki
2014-11-21 15:01 ` Daniel Lezcano
2014-12-04 8:53 ` Daniel Lezcano [this message]
2014-12-16 5:28 ` Len Brown
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=54802121.2030407@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=len.brown@intel.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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).