[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131204015127.GC3298@localhost.localdomain>
Date: Wed, 4 Dec 2013 09:51:27 +0800
From: Baoquan He <bhe@...hat.com>
To: Vivek Goyal <vgoyal@...hat.com>
Cc: mjg59@...f.ucam.org, greg@...ah.com, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org, ebiederm@...ssion.com, hpa@...or.com
Subject: Re: [PATCH 6/6] kexec: Support for Kexec on panic using new system
call
On 12/02/13 at 10:30am, Vivek Goyal wrote:
> On Thu, Nov 28, 2013 at 07:28:16PM +0800, Baoquan He wrote:
>
> [..]
> > > +int crash_copy_backup_region(struct kimage *image)
> > > +{
> >
> > Why need this func be called, backup region has been added into crash
> > segment by kexec_add_buffer, and then buffer copy is done in
> > kimage_load_crash_segment. I think this copy is handled twice. Please
> > correct me if I am wrong.
> >
>
> Hi Bao,
>
> kexec_add_buffer() will copy the backup region but it will happen when
> crash kernel is loaded. We want snapshot of backup region at the time
> of crash and that's why this second call to copy backup region and it
> is executed after the crash.
Did we do this before? And will this region be changed after 1st kernel
boot
>
> Thanks
> Vivek
>
> _______________________________________________
> kexec mailing list
> kexec@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists