On Fri, 28 May 2010 02:18:06 -0700
Arve Hjønnevåg <arve@xxxxxxxxxxx> wrote:
> > IMO, the whole concept is defining 2 modes of operation:
> >
> > 1. user interacts with the device (at least one suspend block active)
> > 2. user doesn't interact with the device (zero suspend block active)
>
> That is a somewhat odd way of looking at it. Yes we have two modes of
> operation, but an active suspend blocker does not mean that the user
> is interacting with the device. The way we use it, the "main" suspend
> blocker is active when the user interacts with the device (controlled
> by writing to /sys/power/state). All other suspend blockers are used
> to prevent suspend when user space has decided that the user is not
> interacting with the device. This includes blocking suspend in the
> kernel on key events which means the user actually is interacting with
> the device, even if user-space has not realized it yet. For other
> events, like an incoming phone call, we block suspend and make some
> noise with the hope that the user will start interacting with the
> device.
Damn. I just want to put some abstract notion around this approach to
power saving.
But one could say instead of "direct" interaction, that every time a
suspend blocker is taken it is "on behalf of the user"?
So if a suspend blocker is taken, because a download is in progress,
it is on behalf of (direct, or indirect) user interaction.
If a suspend blocker is taken, because a key-press has to trickle up to
userspace, it is because of the user.
If a call comes in, a suspend blocker is taken, because the user wants
to receive incomming calls.
So suspend blockers are always a hint to the kernel, that the action is
"on behalf of the user" and it is therefore ok to not suspend the
device?
>
> >
> > In case 1. the device wants _everything_ sheduled as normal (and save
> > maximum possible power, i.e. runtime pm with every technology available
> > now).
> >
> > In case 2. we want nothing sheduled (and save maximum possible power,
> > i.e. suspend)
> >
> OK.
Good. I got this right at least.
>
> > And now, every application and every kernel driver annotates (on behalve
> > of the user) if it (possibly) interacts with the user.
> >
>
> Applications that interact with the user do not normally need to block
> suspend. The user interacting with the device blocks suspend (just
> like with your desktop screen saver). Not every kernel driver needs to
> be annotated either, only potential wakeup events need to be
> annotated.
The applications interacting with the user rely on other parts of
the system to block suspend then.
So it is (in general) not the application which determines if the user
interacts, but other sources (like input-drivers) and possible a
timeout?
>
> > (Is this really the problematic bit, that userspace is giving
> > the kernel hints? Or is it that the hints are called "blocker"?)
> >
> > We can only enter mode 2, if _nothing_ (claims) to interact with the
> > user.
> >
>
> If nothing blocks suspend. The reason to block suspend does not have
> to be direct user interaction.
But couldn't you say, that the suspend blockers are always due to the
user? Or is this too narrow? I mean we talk about a device here. And
the device's purpose is it to serve the user. So it might be better to
say: suspend blockers annotate if a task is needed to fullfill the
devices purpose?
It is an easy to understand concept if one says, the device suspends if
it has nothing to do to further the cause.
I really want to get to a well expressed definition. suspend blockers
block suspend. Shure. Buy why?
>
> > To integrate this with the current way of doing things, i gathered it
> > needs to be implemented as an idle-state that does the suspend()-call?
> >
>
> I think it is better no not confuse this with idle. Since initiating
> suspend will cause the system to become not-idle, I don't think is is
> beneficial to initiate suspend from idle.
I'm not shure. But then again, i'm not too familiar with the kernel. It
sounds like it could save some duplication of effort to integrate
suspend into the idle-framework. "Purpose-fulness" could be just
another measure of "idle".
>
> > Attributes of the idle states could be smth like this:
> >
> > c3
> > cost-to-transition-to-this-state: X
> > powersavings-per-time: Y
> > expected time we stay in this state: relative short, there is a
> > timer sheduled
> > suspend-blockers: ignored
> >
> > suspend
> > cost-to-transition-to-this-state: depends, how much drivers to
> > suspend, how much processes to freeze, how much state to save
> > powersavings-per-time: Y
> > expected time we stay in this state: long, independent of
> > sheduled timers
> > suspend-blockers: must not be activated
> >
> >
> > Now all transitions and opportunistic suspend could be handled by the
> > same algorithms.
> >
> > Would this work?
> >
>
> I'm not sure what you mean.
Yeah. It's a "little bit" handwavy.
But the concept I have in mind:
int what_good_would_it_be_to_go_into_this_state( state )
{
/*
cur_state = get_current_state();
benefit = ( get_power_per_time(cur_state)
- get_power_per_time(state) ) *
get_expected_time_we_stay_there( state );
cost = get_transition_cost(cur_state,state);
return benefit-cost;
*/
}
and a constraint function:
bool is_this_state_possible( state )
{
/*
ret = true;
cur_latency_requirement = get_cur_latency_req();
ret &= (cur_latency_requirement >=state_latency_guaranty( state ) );
ret &= (some other QOS thingy);
return ret;
*/
}
And now, a loop would enter the state which has the biggest score and
is possible at the time.
Afaik this is already implemented for c-states in the cpu_idle drivers?
cheers,
Flo
_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm
