From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Shaohua Li <shaohua.li@intel.com>,
linux acpi <linux-acpi@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>,
Pavel Machek <pavel@suse.cz>
Subject: Re: [linux-pm] Re: [patch] hibernation: utilize ACPI hardware signature
Date: Fri, 04 Jan 2008 09:10:12 +1100 [thread overview]
Message-ID: <477D5D44.5060401@nigel.suspend2.net> (raw)
In-Reply-To: <200801031758.03056.rjw@sisk.pl>
Hi.
Rafael J. Wysocki wrote:
> On Thursday, 3 of January 2008, Nigel Cunningham wrote:
>> Hi.
>>
>> Rafael J. Wysocki wrote:
>>>> I suppose we can always disable this when we start to support hardware
>>>> changing over hibernate (I have ideas in this direction - memory cold
>>>> plugging, for a start).
>>> Well, if we support such features, we won't be following ACPI any more.
>> Mmm. Apparently I'm not as focused on specs as you :).
>>
>> I was starting to think through whether it could make for a new and much
>> faster was to boot live cds - something along the lines of complete
>> redetection of hardware and memory cold plugging. Of course it's only in
>> the 'I wonder if this would be possible' stage at the mo, but seemed at
>> least feasible - keep the e820 tables from boot, make _init routines not
>> get thrown away and do something like the kexec device shutdown etc
>> around an atomic restore.
>>
>> I know there'd be limitations, but perhaps worth thinking about...
>
> Well, what if the new e820 map is incompatible with the old one?
In the worst case, you tell the user about it and carry on with the old
one. Perhaps this would be the killer for the live cd idea - perhaps
e820 maps vary too much, there'd be no possible workaround and this
would never be practical. It's worth at least thinking about, though,
isn't it?
Nigel
next prev parent reply other threads:[~2008-01-03 22:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 6:59 [patch] hibernation: utilize ACPI hardware signature Shaohua Li
2008-01-02 7:37 ` [linux-pm] " Maxim Levitsky
2008-01-02 9:29 ` Johannes Berg
2008-01-03 1:52 ` Shaohua Li
2008-01-02 10:08 ` Erik Andrén
2008-01-02 14:12 ` Rafael J. Wysocki
2008-01-02 21:25 ` [linux-pm] " Nigel Cunningham
2008-01-02 22:18 ` Rafael J. Wysocki
2008-01-03 8:26 ` Nigel Cunningham
2008-01-02 14:05 ` Rafael J. Wysocki
2008-01-02 21:26 ` [linux-pm] " Nigel Cunningham
2008-01-02 22:01 ` Rafael J. Wysocki
2008-01-03 8:31 ` Nigel Cunningham
2008-01-03 16:58 ` Rafael J. Wysocki
2008-01-03 22:10 ` Nigel Cunningham [this message]
2008-01-03 5:36 ` Shaohua Li
2008-01-03 17:04 ` Rafael J. Wysocki
2008-01-04 5:41 ` Shaohua Li
2008-01-04 20:44 ` Rafael J. Wysocki
2008-01-07 1:46 ` Shaohua Li
2008-01-10 23:39 ` Rafael J. Wysocki
2008-01-11 1:07 ` Shaohua Li
2008-01-11 17:20 ` Rafael J. Wysocki
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=477D5D44.5060401@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
--cc=shaohua.li@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