public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	Pavel Machek <pavel@ucw.cz>, Jeremy Maitin-Shepard <jbms@cmu.edu>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: A kexec approach to hibernation
Date: Tue, 12 Jun 2007 08:44:29 +1000	[thread overview]
Message-ID: <1181601870.5064.5.camel@nigel.suspend2.net> (raw)
In-Reply-To: <466CAD2D.3070607@zytor.com>

[-- Attachment #1: Type: text/plain, Size: 580 bytes --]

Hi.

On Sun, 2007-06-10 at 19:02 -0700, H. Peter Anvin wrote:
> Matthew Garrett wrote:
> > No, it only supports ext2 (and reading ext3 as if it's ext2). Right now, 
> > the assumption that syncing during suspend will cause data to hit 
> > something grub can read isn't a safe one.
> 
> I brought this issue up quite a few years ago at an OLS BOF.  We pretty
> much need a "supersync" system call; you can do this by bmapping any
> file on ext3, but having something supported across filesystems would be
> good.

Sounds like a good idea to me.

Regards,

Nigel

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-06-11 22:44 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 20:39 A kexec approach to hibernation Jeremy Maitin-Shepard
2007-06-01 21:39 ` Rafael J. Wysocki
2007-06-01 22:25   ` Jeremy Maitin-Shepard
2007-06-01 23:14     ` Rafael J. Wysocki
2007-06-01 23:54       ` Jeremy Maitin-Shepard
2007-06-02  0:33         ` Rafael J. Wysocki
2007-06-02  1:54           ` Jeremy Maitin-Shepard
2007-06-02  9:22             ` Rafael J. Wysocki
2007-06-04 10:46             ` Pavel Machek
2007-06-04 12:20               ` Matthew Garrett
2007-06-04 13:10                 ` Pavel Machek
2007-06-04 13:16                   ` Matthew Garrett
2007-06-11  2:02                     ` H. Peter Anvin
2007-06-11 22:44                       ` Nigel Cunningham [this message]
2007-06-04 22:09               ` Jeremy Maitin-Shepard
2007-06-04 22:36                 ` Nigel Cunningham
2007-06-05  8:15                   ` Xavier Bestel
2007-06-05  9:34                     ` Stefan Seyfried
2007-06-05  9:40                       ` Xavier Bestel
2007-06-04 22:51                 ` Pavel Machek
2007-06-11 15:07                   ` Jeremy Maitin-Shepard
2007-06-11  3:40             ` Nigel Cunningham
2007-06-11 15:01               ` Jeremy Maitin-Shepard
2007-06-11 15:45                 ` Xavier Bestel
2007-06-11 15:51                   ` Jeremy Maitin-Shepard
2007-06-11 16:03                     ` Xavier Bestel
2007-06-11 17:05                       ` Jeremy Maitin-Shepard
2007-06-04  4:40         ` Vivek Goyal
2007-06-04  5:22           ` Nigel Cunningham
2007-06-04  8:05             ` Rafael J. Wysocki
2007-06-04  8:14               ` Nigel Cunningham
2007-06-04 21:44             ` Jeremy Maitin-Shepard

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=1181601870.5064.5.camel@nigel.suspend2.net \
    --to=nigel@nigel.suspend2.net \
    --cc=hpa@zytor.com \
    --cc=jbms@cmu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=torvalds@osdl.org \
    /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