mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Huang, Ying" <ying.huang@intel.com>,
	nigel@nigel.suspend2.net, Jeremy Maitin-Shepard <jbms@cmu.edu>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH 1/2] Kexec jump: Hibernation image operations
Date: Thu, 12 Jul 2007 22:54:15 +0200	[thread overview]
Message-ID: <200707122254.16695.rjw@sisk.pl> (raw)
In-Reply-To: <20070712093808.GF1866@elf.ucw.cz>

On Thursday, 12 July 2007 11:38, Pavel Machek wrote:
> On Wed 2007-07-11 15:30:34, Huang, Ying wrote:
> > This patch make it possible to have multiple implementations of
> > hibernation image operations such as write, read, check, etc, and they
> > can be switched at run time through writing the
> > "/sys/power/hibernation_image_ops". The uswsusp is the default
> > implementation.
> 
> Umm, so you hook into hibernation_ops, only to run kexec from it?
> 
> Would it make more sense to just run kexec manually, maybe with some
> parameter saying "prepare devices before"?

Well, I think that the $subject patch is unnecessary and confusing.  Instead,
I'd like to have a separate interface to invoke the feature provided by the
second patch.

What the second patch achieves, as far as I understand it, is the ability to be
able to jump between two kernels back and forth, on i386.  Although it may
generally be useful for hibernation, IMO it has very little to it right now,
because _many_ important elements of the infrastructure are still needed.

Greetings,
Rafael


-- 
"Premature optimization is the root of all evil." - Donald Knuth

      reply	other threads:[~2007-07-12 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-11 15:30 Huang, Ying
2007-07-12  9:38 ` Pavel Machek
2007-07-12 20:54   ` Rafael J. Wysocki [this message]

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=200707122254.16695.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=jbms@cmu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=nigel@nigel.suspend2.net \
    --cc=pavel@ucw.cz \
    --cc=ying.huang@intel.com \
    /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

Powered by JetHome