All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Yu <yu.c.chen@intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <len.brown@intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM / hibernate: Introduce snapshot test mode for hibernation
Date: Wed, 13 Jul 2016 18:39:44 +0800	[thread overview]
Message-ID: <57861A70.9090606@intel.com> (raw)
In-Reply-To: <20160713102156.GA14505@atrey.karlin.mff.cuni.cz>



On 2016年07月13日 18:21, Pavel Machek wrote:
> Hi!
>
>> On 2016???07???13??? 17:50, Pavel Machek wrote:
>>> On Thu 2016-07-07 14:40:58, Chen Yu wrote:
>>>> This mode is to verify if the snapshot data written to
>>>> swap device can be successfully restored to memory. It
>>>> is useful to ease the debugging process on hibernation,
>>>> since this mode can not only bypass the BIOSen/bootloader,
>>>> but also the system re-initialization.
>>>>
>>>> For example:
>>>> $ sudo echo snapshot > /sys/power/disk
>>>> $ sudo echo disk > /sys/power/state
>>>>
>>>> /* manual resume.*/
>>>> $ sudo echo 8:3 > /sys/power/resume
>>> Your examples will not work, will they?
>> It works on my platform, although I did not tested it for too many
>> rounds.
> Please check again:
>
> sudo echo disk > /sys/power/state
> -bash: /sys/power/state: Permission denied
>
> ...because bash does the open, not echo.
Sorry, my bad, I logined as root:P
I'll rewrite the commit log.
>>> This is also quite tricky/dangerous. If you do this with filesystems
>>> mounted R/W, it is "good bye, filesystems".
>> Ah, yes, this is quite tricky, maybe we can use this option as a
>> debug method,
>> for example, boot with rootfs = initrd, without mounting any disks,
>> and then swapon the swap device, and do a testing. This should be safer?
> Yeah, that's the way. Read-only root is other option.
>
>>> I guess updating documentation would be welcome from my side,
>>> otherwise it should be ok.
>> OK, I'll  update the documents.
> Just add fat warning into the documentation.
OK.
> Thanks,
> 									Pavel


  reply	other threads:[~2016-07-13 10:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07  6:40 [PATCH] PM / hibernate: Introduce snapshot test mode for hibernation Chen Yu
2016-07-13  9:50 ` Pavel Machek
2016-07-13 10:20   ` Chen Yu
2016-07-13 10:21     ` Pavel Machek
2016-07-13 10:39       ` Chen Yu [this message]
2016-07-13 17:01         ` Pavel Machek
2016-07-13 20:04           ` Rafael J. Wysocki
2016-07-13 20:26             ` Pavel Machek
2016-07-13 20:44               ` Rafael J. Wysocki
2016-07-13 21:45                 ` Pavel Machek
2016-07-13 22:00                   ` Rafael J. Wysocki
2016-07-13 22:18                     ` Rafael J. Wysocki
2016-07-14 10:44                       ` Chen Yu

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=57861A70.9090606@intel.com \
    --to=yu.c.chen@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.