From: Vivek Goyal <vgoyal@redhat.com>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Pavel Machek <pavel@ucw.cz>,
nigel@nigel.suspend2.net, "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATCH 2/2] kexec jump -v10: save/restore device state
Date: Wed, 28 May 2008 08:57:42 -0400 [thread overview]
Message-ID: <20080528125742.GA3884@redhat.com> (raw)
In-Reply-To: <1211449099.12819.15.camel@caritas-dev.intel.com>
On Thu, May 22, 2008 at 05:38:19PM +0800, Huang, Ying wrote:
[..]
> Known issues:
>
> - Can not work with the new devices hibernation operations in
> 2.6.26-rc2-mm1 so far. Working on this now.
>
> - APIC is not put into legacy mode during kexec, so kexec may failed
> (no IRQ) if APIC is not put into legacy mode.
>
> - The suspend/resume callback of device drivers are used to put
> devices into quiescent state. This will unnecessarily (possibly
> harmfully) put devices into low power state. This is intended to be
> solved by separating device quiesce/unquiesce callback from the
> device suspend/resume callback.
>
> - Because the segment number supported by sys_kexec_load is limited,
> hibernation image with many segments may not be load. This is
> planned to be eliminated by adding a new flag to sys_kexec_load to
> make a image can be loaded with multiple sys_kexec_load invoking.
>
>
These two patches look good to me. I think once you have worked out
issues with IOAPIC and generated patches for compatibility with
new suspend/resume callbacks, these patches are good enough to get
some testing going on in -mm tree.
I will also test out -v10 very soon.
Thanks
Vivek
prev parent reply other threads:[~2008-05-28 12:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 9:38 [PATCH 2/2] kexec jump -v10: save/restore device state Huang, Ying
2008-05-28 12:57 ` Vivek Goyal [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=20080528125742.GA3884@redhat.com \
--to=vgoyal@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=nigel@nigel.suspend2.net \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--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