[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9fbbe4fa9aa0e202909c2ba6eefdb22ef4f2b1d8.camel@intel.com>
Date: Wed, 6 Feb 2019 15:31:36 +0000
From: "Pan, Harry" <harry.pan@...el.com>
To: "pavel@....cz" <pavel@....cz>
CC: "Brown, Len" <len.brown@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"gs0622@...il.com" <gs0622@...il.com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"rjw@...ysocki.net" <rjw@...ysocki.net>
Subject: Re: [PATCH] PM / suspend: measure the time of filesystem syncing
> The backdrop is some stress test script of suspend/resume, like
> Chrome
> OS, is designed to program an expected RTC wake-alarm then issue
> suspend command, while in rare case (or buggy software), the
> filesystem
> sync could cost longer time in seconds, this consumes the alarm
> budget
> causes suspend aborting, it could be abstruse to production line
> developers to realize it is not a platform issue in terms of drivers
> suspending; given a such metric might make the communication easier,
> this is my intuition.
>
apologize rephrase: my intuition -> my motivation
Powered by blists - more mailing lists