On 11/13/2014 03:56 PM, Lorenzo Pieralisi wrote:
On Wed, Nov 12, 2014 at 03:03:50PM +, Daniel Lezcano wrote:
The only place where the time is invalid is when the ACPI_CSTATE_FFH entry
method is not set. Otherwise for all the drivers, the time can be correctly
measured.
Instead of
On 11/13/2014 03:56 PM, Lorenzo Pieralisi wrote:
On Wed, Nov 12, 2014 at 03:03:50PM +, Daniel Lezcano wrote:
The only place where the time is invalid is when the ACPI_CSTATE_FFH entry
method is not set. Otherwise for all the drivers, the time can be correctly
measured.
Instead of
On Wednesday, November 12, 2014 04:03:50 PM Daniel Lezcano wrote:
> The only place where the time is invalid is when the ACPI_CSTATE_FFH entry
> method is not set. Otherwise for all the drivers, the time can be correctly
> measured.
>
> Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in
On Wednesday, November 12, 2014 04:03:50 PM Daniel Lezcano wrote:
The only place where the time is invalid is when the ACPI_CSTATE_FFH entry
method is not set. Otherwise for all the drivers, the time can be correctly
measured.
Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in all
On 11/13/2014 03:56 PM, Lorenzo Pieralisi wrote:
On Wed, Nov 12, 2014 at 03:03:50PM +, Daniel Lezcano wrote:
The only place where the time is invalid is when the ACPI_CSTATE_FFH entry
method is not set. Otherwise for all the drivers, the time can be correctly
measured.
Instead of
On Wed, Nov 12, 2014 at 03:03:50PM +, Daniel Lezcano wrote:
> The only place where the time is invalid is when the ACPI_CSTATE_FFH entry
> method is not set. Otherwise for all the drivers, the time can be correctly
> measured.
>
> Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in all
On Wed, Nov 12, 2014 at 03:03:50PM +, Daniel Lezcano wrote:
The only place where the time is invalid is when the ACPI_CSTATE_FFH entry
method is not set. Otherwise for all the drivers, the time can be correctly
measured.
Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in all the
On 11/13/2014 03:56 PM, Lorenzo Pieralisi wrote:
On Wed, Nov 12, 2014 at 03:03:50PM +, Daniel Lezcano wrote:
The only place where the time is invalid is when the ACPI_CSTATE_FFH entry
method is not set. Otherwise for all the drivers, the time can be correctly
measured.
Instead of
The only place where the time is invalid is when the ACPI_CSTATE_FFH entry
method is not set. Otherwise for all the drivers, the time can be correctly
measured.
Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in all the drivers
for all the states, just invert the logic by replacing it by
The only place where the time is invalid is when the ACPI_CSTATE_FFH entry
method is not set. Otherwise for all the drivers, the time can be correctly
measured.
Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in all the drivers
for all the states, just invert the logic by replacing it by
10 matches
Mail list logo