huang ying wrote:
On 9/21/07, Mika Penttilä <[EMAIL PROTECTED]> wrote:
huang ying wrote:
On 9/21/07, Mika Penttilä <[EMAIL PROTECTED]> wrote:
Usage:
1. Compile kernel with following options selected:
CONFIG_X86_32=y
CONFIG_RELOCATABLE=y # not needed strictly, but it is more
huang ying wrote:
On 9/21/07, Mika Penttilä <[EMAIL PROTECTED]> wrote:
Usage:
1. Compile kernel with following options selected:
CONFIG_X86_32=y
CONFIG_RELOCATABLE=y # not needed strictly, but it is more convenient with it
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y # only needed by kexeced kernel
Usage:
1. Compile kernel with following options selected:
CONFIG_X86_32=y
CONFIG_RELOCATABLE=y # not needed strictly, but it is more convenient with it
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y # only needed by kexeced kernel to save/restore memory image
CONFIG_PM=y
CONFIG_KEXEC_JUMP=y
2. Download
On Fri, 2007-09-21 at 10:43 +0200, Stefan Rompf wrote:
> Am Donnerstag, 20. September 2007 07:34 schrieb Huang, Ying:
>
> > The hibernation procedure with the patch set is as follow:
> >
> > 1. Boot a kernel A
> >
> > 2. Work under kernel A
> >
> > 3. Kexec another kernel B (crash dump enabled)
Am Donnerstag, 20. September 2007 07:34 schrieb Huang, Ying:
> The hibernation procedure with the patch set is as follow:
>
> 1. Boot a kernel A
>
> 2. Work under kernel A
>
> 3. Kexec another kernel B (crash dump enabled) in kernel A.
>From a short glance over current Linus'
Am Donnerstag, 20. September 2007 07:34 schrieb Huang, Ying:
The hibernation procedure with the patch set is as follow:
1. Boot a kernel A
2. Work under kernel A
3. Kexec another kernel B (crash dump enabled) in kernel A.
From a short glance over current Linus'
On Fri, 2007-09-21 at 10:43 +0200, Stefan Rompf wrote:
Am Donnerstag, 20. September 2007 07:34 schrieb Huang, Ying:
The hibernation procedure with the patch set is as follow:
1. Boot a kernel A
2. Work under kernel A
3. Kexec another kernel B (crash dump enabled) in kernel A.
Usage:
1. Compile kernel with following options selected:
CONFIG_X86_32=y
CONFIG_RELOCATABLE=y # not needed strictly, but it is more convenient with it
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y # only needed by kexeced kernel to save/restore memory image
CONFIG_PM=y
CONFIG_KEXEC_JUMP=y
2. Download
huang ying wrote:
On 9/21/07, Mika Penttilä [EMAIL PROTECTED] wrote:
Usage:
1. Compile kernel with following options selected:
CONFIG_X86_32=y
CONFIG_RELOCATABLE=y # not needed strictly, but it is more convenient with it
CONFIG_KEXEC=y
CONFIG_CRASH_DUMP=y # only needed by kexeced kernel to
huang ying wrote:
On 9/21/07, Mika Penttilä [EMAIL PROTECTED] wrote:
huang ying wrote:
On 9/21/07, Mika Penttilä [EMAIL PROTECTED] wrote:
Usage:
1. Compile kernel with following options selected:
CONFIG_X86_32=y
CONFIG_RELOCATABLE=y # not needed strictly, but it is more
Kexec base hibernation has some potential advantages over uswsusp and
TuxOnIce (suspend2). Some most obvious advantages are:
1. The hibernation image size can exceed half of memory size easily.
2. The hibernation image can be written to and read from almost
anywhere, such as USB disk, NFS.
Kexec base hibernation has some potential advantages over uswsusp and
TuxOnIce (suspend2). Some most obvious advantages are:
1. The hibernation image size can exceed half of memory size easily.
2. The hibernation image can be written to and read from almost
anywhere, such as USB disk, NFS.
Huang, Ying wrote:
On Mon, 2007-08-27 at 09:28 +0800, Hu, Fenghua wrote:
One quick question is, can it improve hiberation/wakeup time?
In general, for kexec based hibernation, what increases
hibernation/wakeup time:
- One extra Linux boot is needed to hibernate and wakeup.
What decreases
Huang, Ying wrote:
On Mon, 2007-08-27 at 09:28 +0800, Hu, Fenghua wrote:
One quick question is, can it improve hiberation/wakeup time?
In general, for kexec based hibernation, what increases
hibernation/wakeup time:
- One extra Linux boot is needed to hibernate and wakeup.
What decreases
On Mon, 2007-08-27 at 13:15 +, Pavel Machek wrote:
> Hi!
>
> > >> > Does this make sense?
> > >>
> > >> Yes, this is a sensible optimization. But I think it may be better to
> > >> make bootloader load kernel D directly into a specified memory location.
> > >> For example, we can add a
Hi!
> >> > Does this make sense?
> >>
> >> Yes, this is a sensible optimization. But I think it may be better to
> >> make bootloader load kernel D directly into a specified memory location.
> >> For example, we can add a option to "kernel" command of grub.
> >>
> >> And, I think we can do
Pavel Machek <[EMAIL PROTECTED]> writes:
> Hi!
>
>> > Does this make sense?
>>
>> Yes, this is a sensible optimization. But I think it may be better to
>> make bootloader load kernel D directly into a specified memory location.
>> For example, we can add a option to "kernel" command of grub.
>>
Hi!
> > Does this make sense?
>
> Yes, this is a sensible optimization. But I think it may be better to
> make bootloader load kernel D directly into a specified memory location.
> For example, we can add a option to "kernel" command of grub.
>
> And, I think we can do more in bootloader. Such
On Mon, Aug 27, 2007 at 02:18:49PM +0800, Huang, Ying wrote:
[..]
> >
> > If one compiles the kernel C to boot from reserved memory area (subset
> > of memory area used by kernel B), then I can skip the step of kexecing
> > from C to D? (COFIG_PHYSICAL_START)
>
> Yes. I think so.
>
> >
On Mon, 2007-08-27 at 10:30 +0530, Vivek Goyal wrote:
> On Mon, Aug 27, 2007 at 09:14:05AM +0800, Huang, Ying wrote:
> > Kexec base hibernation has some potential advantages over uswsusp and
> > TuxOnIce (suspend2). Some most obvious advantages are:
> >
> > 1. The hibernation image size can
On Mon, 2007-08-27 at 10:30 +0530, Vivek Goyal wrote:
On Mon, Aug 27, 2007 at 09:14:05AM +0800, Huang, Ying wrote:
Kexec base hibernation has some potential advantages over uswsusp and
TuxOnIce (suspend2). Some most obvious advantages are:
1. The hibernation image size can exceed half of
On Mon, Aug 27, 2007 at 02:18:49PM +0800, Huang, Ying wrote:
[..]
If one compiles the kernel C to boot from reserved memory area (subset
of memory area used by kernel B), then I can skip the step of kexecing
from C to D? (COFIG_PHYSICAL_START)
Yes. I think so.
Alternatively, can
Hi!
Does this make sense?
Yes, this is a sensible optimization. But I think it may be better to
make bootloader load kernel D directly into a specified memory location.
For example, we can add a option to kernel command of grub.
And, I think we can do more in bootloader. Such as we can
Pavel Machek [EMAIL PROTECTED] writes:
Hi!
Does this make sense?
Yes, this is a sensible optimization. But I think it may be better to
make bootloader load kernel D directly into a specified memory location.
For example, we can add a option to kernel command of grub.
And, I think we
Hi!
Does this make sense?
Yes, this is a sensible optimization. But I think it may be better to
make bootloader load kernel D directly into a specified memory location.
For example, we can add a option to kernel command of grub.
And, I think we can do more in bootloader. Such as
On Mon, 2007-08-27 at 13:15 +, Pavel Machek wrote:
Hi!
Does this make sense?
Yes, this is a sensible optimization. But I think it may be better to
make bootloader load kernel D directly into a specified memory location.
For example, we can add a option to kernel command of
On Mon, Aug 27, 2007 at 09:14:05AM +0800, Huang, Ying wrote:
> Kexec base hibernation has some potential advantages over uswsusp and
> TuxOnIce (suspend2). Some most obvious advantages are:
>
> 1. The hibernation image size can exceed half of memory size easily.
>
> 2. The hibernation image can
emy
> Maitin-Shepard; Alan Stern
> Cc: [EMAIL PROTECTED]; Kexec Mailing List; linux-kernel@vger.kernel.org
> Subject: [linux-pm] [RFC][PATCH 0/2 -mm] kexec based hibernation
>
> Kexec base hibernation has some potential advantages over uswsusp and
> TuxOnIce (suspen
Maitin-Shepard; Alan Stern
Cc: [EMAIL PROTECTED]; Kexec Mailing List; linux-kernel@vger.kernel.org
Subject: [linux-pm] [RFC][PATCH 0/2 -mm] kexec based hibernation
Kexec base hibernation has some potential advantages over uswsusp and
TuxOnIce (suspend2). Some most obvious advantages are:
1
Kexec base hibernation has some potential advantages over uswsusp and
TuxOnIce (suspend2). Some most obvious advantages are:
1. The hibernation image size can exceed half of memory size easily.
2. The hibernation image can be written to and read from almost
anywhere, such as USB disk, NFS.
Kexec base hibernation has some potential advantages over uswsusp and
TuxOnIce (suspend2). Some most obvious advantages are:
1. The hibernation image size can exceed half of memory size easily.
2. The hibernation image can be written to and read from almost
anywhere, such as USB disk, NFS.
Maitin-Shepard; Alan Stern
Cc: [EMAIL PROTECTED]; Kexec Mailing List; linux-kernel@vger.kernel.org
Subject: [linux-pm] [RFC][PATCH 0/2 -mm] kexec based hibernation
Kexec base hibernation has some potential advantages over uswsusp and
TuxOnIce (suspend2). Some most obvious advantages are:
1
: [EMAIL PROTECTED]; Kexec Mailing List; linux-kernel@vger.kernel.org
Subject: [linux-pm] [RFC][PATCH 0/2 -mm] kexec based hibernation
Kexec base hibernation has some potential advantages over uswsusp and
TuxOnIce (suspend2). Some most obvious advantages are:
1. The hibernation image size
On Mon, Aug 27, 2007 at 09:14:05AM +0800, Huang, Ying wrote:
Kexec base hibernation has some potential advantages over uswsusp and
TuxOnIce (suspend2). Some most obvious advantages are:
1. The hibernation image size can exceed half of memory size easily.
2. The hibernation image can be
34 matches
Mail list logo
