On Wed, Feb 13, 2019 at 12:21 AM Rafael J. Wysocki <[email protected]> wrote: > > On Wed, Feb 6, 2019 at 4:57 PM Harry Pan <[email protected]> wrote: > > > > This patch gives the reader an intuitive metric of the time cost by > > the kernel issuing a filesystem sync during suspend; although developer > > can guess by the timestamp of next log or enable the ftrace power event > > for manual calculation, this manner is easier to read and benefits the > > automatic script. > > > > v2: simplify the variables, apply the simplest form of ktime API. > > > > Signed-off-by: Harry Pan <[email protected]> > > --- > > kernel/power/suspend.c | 7 ++++++- > > 1 file changed, 6 insertions(+), 1 deletion(-) > > > > diff --git a/kernel/power/suspend.c b/kernel/power/suspend.c > > index 0bd595a0b610..87c0073f0c9d 100644 > > --- a/kernel/power/suspend.c > > +++ b/kernel/power/suspend.c > > @@ -550,6 +550,8 @@ static void suspend_finish(void) > > static int enter_state(suspend_state_t state) > > { > > int error; > > + ktime_t start; > > + unsigned int elapsed_msecs; > > You only need these two if CONFIG_SUSPEND_SKIP_SYNC is set, ->
s/set/unset/ Sorry for the confusion.
