mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Mario.Limonciello@dell.com>
To: <rjw@rjwysocki.net>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] power/hibernate: Make passing hibernate offsets more friendly
Date: Mon, 26 Mar 2018 07:17:22 +0000	[thread overview]
Message-ID: <b3e9a7ad5dfc4348a8b017110e8ba032@ausx13mpc120.AMER.DELL.COM> (raw)
In-Reply-To: <1854392.I8WPNng6r5@aspire.rjw.lan>

> -----Original Message-----
> From: Rafael J. Wysocki [mailto:rjw@rjwysocki.net]
> Sent: Monday, March 19, 2018 5:11 AM
> To: Limonciello, Mario <Mario_Limonciello@Dell.com>
> Cc: linux-acpi@vger.kernel.org; LKML <linux-kernel@vger.kernel.org>
> Subject: Re: [PATCH] power/hibernate: Make passing hibernate offsets more friendly
> 
> On Tuesday, March 6, 2018 11:53:40 AM CET Mario Limonciello wrote:
> > Currently the only way to specify a hibernate offset for a
> > swap file is on the kernel command line.
> >
> > Add a new /sys/power/disk_offset that lets userspace
> > specify the offset and disk to use when initiating a hibernate
> > cycle.
> >
> > Also split up the parsing routine to re-use the same code
> > for the /sys/power/resume and /sys/power/disk_offset parsing.
> >
> > Signed-off-by: Mario Limonciello <mario.limonciello@dell.com>
> 
> Well, IMO /sys/power/resume and /sys/power/disk_offset would be confusingly
> similar after this patch.

Yeah they do function pretty similarly.

> 
> I wonder if adding a resume_offset sysfs attr to simply allow the value of
> resume offset alone to be passed to the kernel at run time (in addition to
> the command line) would work?
> 
> Thanks!

I guess what's your expected flow for how the disk gets selected though?  Should
the kernel be "guessing" which disk to use?

Or should userspace be setting offset via /sys/power/resume_offset followed by
disk in /sys/power/resume (which will show an error in syslog about no partition
found)

If the latter, then I'd like to also modify the behavior to downgrade that missing
hibernate partition to debug instead too.

  reply	other threads:[~2018-03-26  7:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 10:53 Mario Limonciello
2018-03-19 10:11 ` Rafael J. Wysocki
2018-03-26  7:17   ` Mario.Limonciello [this message]
2018-03-26  9:37     ` Rafael J. Wysocki
2018-03-26  9:41       ` Mario.Limonciello

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=b3e9a7ad5dfc4348a8b017110e8ba032@ausx13mpc120.AMER.DELL.COM \
    --to=mario.limonciello@dell.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®