On Tue, 2007-12-11 at 02:27 -0700, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
>
> > On Mon, 2007-12-10 at 19:25 -0700, Eric W. Biederman wrote:
> >> "Huang, Ying" <[EMAIL PROTECTED]> writes:
> > [...]
> >> > /*
> >> > * Do not allocate memory (or fail in any way) in ma
On Tue, 2007-12-11 at 02:27 -0700, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
>
> > On Mon, 2007-12-10 at 19:25 -0700, Eric W. Biederman wrote:
> >> "Huang, Ying" <[EMAIL PROTECTED]> writes:
> > [...]
> >> > /*
> >> > * Do not allocate memory (or fail in any way) in ma
"Huang, Ying" <[EMAIL PROTECTED]> writes:
> On Mon, 2007-12-10 at 19:25 -0700, Eric W. Biederman wrote:
>> "Huang, Ying" <[EMAIL PROTECTED]> writes:
> [...]
>> > /*
>> > * Do not allocate memory (or fail in any way) in machine_kexec().
>> > * We are past the point of no return, committed to r
On Mon, 2007-12-10 at 19:25 -0700, Eric W. Biederman wrote:
> "Huang, Ying" <[EMAIL PROTECTED]> writes:
[...]
> > /*
> > * Do not allocate memory (or fail in any way) in machine_kexec().
> > * We are past the point of no return, committed to rebooting now.
> > */
> > -NORET_TYPE void machine
"Huang, Ying" <[EMAIL PROTECTED]> writes:
> This patch implements the functionality of jumping between the kexeced
> kernel and the original kernel.
>
> To support jumping between two kernels, before jumping to (executing)
> the new kernel and jumping back to the original kernel, the devices
> are
On Mon, 2007-12-10 at 17:31 -0500, Vivek Goyal wrote:
> [..]
> >
> > -#define KEXEC_ON_CRASH 0x0001
> > -#define KEXEC_ARCH_MASK 0x
> > +#define KEXEC_ON_CRASH 0x0001
> > +#define KEXEC_PRESERVE_CPU 0x0002
> > +#define KEXEC_PRESERVE_CPU_EXT 0x0004
> > +#d
On Mon, 2007-12-10 at 14:55 -0500, Vivek Goyal wrote:
> On Fri, Dec 07, 2007 at 03:53:30PM +, Huang, Ying wrote:
> > This patch implements the functionality of jumping between the kexeced
> > kernel and the original kernel.
> >
>
> Hi,
>
> I am just going through your patches and trying to u
On Fri, Dec 07, 2007 at 03:53:30PM +, Huang, Ying wrote:
> This patch implements the functionality of jumping between the kexeced
> kernel and the original kernel.
>
> To support jumping between two kernels, before jumping to (executing)
> the new kernel and jumping back to the original kernel
On Fri, Dec 07, 2007 at 03:53:30PM +, Huang, Ying wrote:
> This patch implements the functionality of jumping between the kexeced
> kernel and the original kernel.
>
Hi,
I am just going through your patches and trying to understand it. Don't
understand many things. Asking is easy so here you
"Rafael J. Wysocki" <[EMAIL PROTECTED]> writes:
>> I'm not kexec hacker... but maybe this is in good enough state to be
>> merged? It is useful on its own: kexec jump and back means we can dump
>> system then continue running, for example...
>
> As far as I'm concerned, patches [1/4] and [2/4] can
On Sunday, 9 of December 2007, Pavel Machek wrote:
> Hi!
>
> > This patch implements the functionality of jumping between the kexeced
> > kernel and the original kernel.
> >
> > To support jumping between two kernels, before jumping to (executing)
> > the new kernel and jumping back to the origin
Hi!
> This patch implements the functionality of jumping between the kexeced
> kernel and the original kernel.
>
> To support jumping between two kernels, before jumping to (executing)
> the new kernel and jumping back to the original kernel, the devices
> are put into quiescent state, and the st
This patch implements the functionality of jumping between the kexeced
kernel and the original kernel.
To support jumping between two kernels, before jumping to (executing)
the new kernel and jumping back to the original kernel, the devices
are put into quiescent state, and the state of devices an
13 matches
Mail list logo
