All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Huang, Ying" <ying.huang@intel.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: nigel@nigel.suspend2.net,
	Kexec Mailing List <kexec@lists.infradead.org>,
	linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Pavel Machek <pavel@ucw.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH -mm 2/2] kexec jump -v11: save/restore device state
Date: Thu, 12 Jun 2008 08:53:39 +0800	[thread overview]
Message-ID: <1213232019.21353.8.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <20080611163026.GG6450@redhat.com>

On Wed, 2008-06-11 at 12:30 -0400, Vivek Goyal wrote:
[...]
> > Usage example of simple hibernation:
> > 
> > 1. Compile and install patched kernel with following options selected:
> > 
> > CONFIG_X86_32=y
> > CONFIG_RELOCATABLE=y
> > CONFIG_KEXEC=y
> > CONFIG_CRASH_DUMP=y
> > CONFIG_PM=y
> > 
> > 2. Build an initramfs image contains kexec-tool and makedumpfile, or
> >    download the pre-built initramfs image, called rootfs.gz in
> >    following text.
> > 
> > 3. Prepare a partition to save memory image of original kernel, called
> >    hibernating partition in following text.
> > 
> > 4. Boot kernel compiled in step 1 (kernel A).
> > 
> > 5. In the kernel A, load kernel compiled in step 1 (kernel B) with
> >    /sbin/kexec. The shell command line can be as follow:
> > 
> >    /sbin/kexec --load-preserve-context /boot/bzImage --mem-min=0x100000
> >      --mem-max=0xffffff --initrd=rootfs.gz
> > 
> > 6. Boot the kernel B with following shell command line:
> > 
> >    /sbin/kexec -e
> > 
> > 7. The kernel B will boot as normal kexec. In kernel B the memory
> >    image of kernel A can be saved into hibernating partition as
> >    follow:
> > 
> >    jump_back_entry=`cat /proc/cmdline | tr ' ' '\n' | grep kexec_jump_back_entry | cut -d '='`
> >    echo $jump_back_entry > kexec_jump_back_entry
> >    cp /proc/vmcore dump.elf
> > 
> >    Then you can shutdown the machine as normal.
> > 
> > 8. Boot kernel compiled in step 1 (kernel C). Use the rootfs.gz as
> >    root file system.
> > 
> 
> One of the concerns raised by hibernation people in the past was to use
> single boot loader entry to boot normally as well while resuming a kernel.
> 
> So in this case a user either needs to maintain two boot-loader entries
> or modify it on the fly. I wished there was a better way to handle that.

Now it is not needed to have two boot-loader entries, just one is
enough. Step 4 and step 8 can share the same boot-loader entries. The
rootfs.gz can be the normal initramfs or initrd when deployment. In
rootfs.gz, if there is a valid hibernation image, the hibernated system
will be restored, otherwise, normal boot process follows.


> I am more interested in ability to have multiple kernel loaded in RAM
> and capability to switch between them. Allows me to take non-disruptive
> core dumps and somebody wanted to snapshots the kernels. That should
> still work.
> 
> 
> [..]
> > --- a/arch/x86/kernel/machine_kexec_32.c
> > +++ b/arch/x86/kernel/machine_kexec_32.c
> > @@ -125,6 +125,12 @@ void machine_kexec(struct kimage *image)
> >  	/* Interrupts aren't acceptable while we reboot */
> >  	local_irq_disable();
> >  
> > +	if (image->preserve_context) {
> > +#ifdef CONFIG_X86_IO_APIC
> > +		disable_IO_APIC();
> > +#endif
> 
> I think it would be a good idea to put some kind of comment here. We
> need to put APICs in legacy mode so that we can get timer interrupts
> in second kernel. kexec/kdump paths already have calls to
> disable_IO_APIC() in one form or other. kexec jump path also needs one.

OK. I will add it.

Best Regards,
Huang Ying


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: "Huang, Ying" <ying.huang@intel.com>
To: Vivek Goyal <vgoyal@redhat.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 -mm 2/2] kexec jump -v11: save/restore device state
Date: Thu, 12 Jun 2008 08:53:39 +0800	[thread overview]
Message-ID: <1213232019.21353.8.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <20080611163026.GG6450@redhat.com>

On Wed, 2008-06-11 at 12:30 -0400, Vivek Goyal wrote:
[...]
> > Usage example of simple hibernation:
> > 
> > 1. Compile and install patched kernel with following options selected:
> > 
> > CONFIG_X86_32=y
> > CONFIG_RELOCATABLE=y
> > CONFIG_KEXEC=y
> > CONFIG_CRASH_DUMP=y
> > CONFIG_PM=y
> > 
> > 2. Build an initramfs image contains kexec-tool and makedumpfile, or
> >    download the pre-built initramfs image, called rootfs.gz in
> >    following text.
> > 
> > 3. Prepare a partition to save memory image of original kernel, called
> >    hibernating partition in following text.
> > 
> > 4. Boot kernel compiled in step 1 (kernel A).
> > 
> > 5. In the kernel A, load kernel compiled in step 1 (kernel B) with
> >    /sbin/kexec. The shell command line can be as follow:
> > 
> >    /sbin/kexec --load-preserve-context /boot/bzImage --mem-min=0x100000
> >      --mem-max=0xffffff --initrd=rootfs.gz
> > 
> > 6. Boot the kernel B with following shell command line:
> > 
> >    /sbin/kexec -e
> > 
> > 7. The kernel B will boot as normal kexec. In kernel B the memory
> >    image of kernel A can be saved into hibernating partition as
> >    follow:
> > 
> >    jump_back_entry=`cat /proc/cmdline | tr ' ' '\n' | grep kexec_jump_back_entry | cut -d '='`
> >    echo $jump_back_entry > kexec_jump_back_entry
> >    cp /proc/vmcore dump.elf
> > 
> >    Then you can shutdown the machine as normal.
> > 
> > 8. Boot kernel compiled in step 1 (kernel C). Use the rootfs.gz as
> >    root file system.
> > 
> 
> One of the concerns raised by hibernation people in the past was to use
> single boot loader entry to boot normally as well while resuming a kernel.
> 
> So in this case a user either needs to maintain two boot-loader entries
> or modify it on the fly. I wished there was a better way to handle that.

Now it is not needed to have two boot-loader entries, just one is
enough. Step 4 and step 8 can share the same boot-loader entries. The
rootfs.gz can be the normal initramfs or initrd when deployment. In
rootfs.gz, if there is a valid hibernation image, the hibernated system
will be restored, otherwise, normal boot process follows.


> I am more interested in ability to have multiple kernel loaded in RAM
> and capability to switch between them. Allows me to take non-disruptive
> core dumps and somebody wanted to snapshots the kernels. That should
> still work.
> 
> 
> [..]
> > --- a/arch/x86/kernel/machine_kexec_32.c
> > +++ b/arch/x86/kernel/machine_kexec_32.c
> > @@ -125,6 +125,12 @@ void machine_kexec(struct kimage *image)
> >  	/* Interrupts aren't acceptable while we reboot */
> >  	local_irq_disable();
> >  
> > +	if (image->preserve_context) {
> > +#ifdef CONFIG_X86_IO_APIC
> > +		disable_IO_APIC();
> > +#endif
> 
> I think it would be a good idea to put some kind of comment here. We
> need to put APICs in legacy mode so that we can get timer interrupts
> in second kernel. kexec/kdump paths already have calls to
> disable_IO_APIC() in one form or other. kexec jump path also needs one.

OK. I will add it.

Best Regards,
Huang Ying


  reply	other threads:[~2008-06-12  0:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10  7:15 [PATCH -mm 2/2] kexec jump -v11: save/restore device state Huang, Ying
2008-06-10  7:15 ` Huang, Ying
2008-06-10 18:01 ` Len Brown
2008-06-10 18:01 ` [linux-pm] " Len Brown
2008-06-10 18:01   ` Len Brown
2008-06-11  1:01   ` Huang, Ying
2008-06-11  1:01   ` [linux-pm] " Huang, Ying
2008-06-11  1:01     ` Huang, Ying
2008-06-11  8:21     ` Len Brown
2008-06-11  8:21       ` Len Brown
2008-06-11  9:46       ` Huang, Ying
2008-06-11  9:46       ` [linux-pm] " Huang, Ying
2008-06-11  9:46         ` Huang, Ying
2008-06-11  8:21     ` Len Brown
2008-06-13 18:05     ` [linux-pm] " Vivek Goyal
2008-06-13 18:05       ` Vivek Goyal
2008-06-16  1:29       ` Huang, Ying
2008-06-16  1:29       ` [linux-pm] " Huang, Ying
2008-06-16  1:29         ` Huang, Ying
2008-06-13 18:05     ` Vivek Goyal
2008-06-11 16:30 ` Vivek Goyal
2008-06-11 16:30   ` Vivek Goyal
2008-06-12  0:53   ` Huang, Ying [this message]
2008-06-12  0:53     ` Huang, Ying
2008-06-12 13:02     ` Vivek Goyal
2008-06-12 13:02       ` Vivek Goyal
2008-06-13  1:18       ` Huang, Ying
2008-06-13  1:18         ` Huang, Ying
2008-06-13  1:18       ` Huang, Ying
2008-06-12 13:02     ` Vivek Goyal
2008-06-12  0:53   ` Huang, Ying
2008-06-11 16:30 ` Vivek Goyal
  -- strict thread matches above, loose matches on Subject: below --
2008-06-10  7:15 Huang, Ying

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=1213232019.21353.8.camel@caritas-dev.intel.com \
    --to=ying.huang@intel.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=vgoyal@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.