From: ebiederm@xmission.com (Eric W. Biederman)
To: Andy Pfiffer <andyp@osdl.org>
Cc: Andrew Morton <akpm@digeo.com>, linux-kernel@vger.kernel.org
Subject: Re: [KEXEC][2.5.69] Re: Updated kexec diffs...
Date: 13 May 2003 23:11:33 -0600 [thread overview]
Message-ID: <m1k7cu3yey.fsf@frodo.biederman.org> (raw)
In-Reply-To: <1052861167.1324.15.camel@andyp.pdx.osdl.net>
Andy Pfiffer <andyp@osdl.org> writes:
> On Sun, 2003-05-11 at 17:26, Eric W. Biederman wrote:
> > This is my next round of kexec inspired kernel patches.
> >
> > kexec seems good at reproducing what are otherwise almost
> > inaccessible corner cases in the kernel reboot/initialization code paths.
> >
> > Also available at:
> > http://www.xmission.com/~ebiederm/files/kexec/
>
> Eric,
>
> Good news: I have tried your patchset on a 2-way system, and kexec
> worked.
>
> Mixed news: I didn't get any console output after the last printk in
> kexec ("Starting new kernel"), nor did I get any console output during
> the reboot. Other than that, the system rebooted fine and went
> multi-user (complete with graphical login and networking). Strange.
Very strange as nothing fundamental changed.
The only thing I did was inline use_mm into kexec piece. And
to make the cpu shutdown code safe from an interrupt context.
> I've got two other systems to test this on, and I'll report when I have
> results. I have attached my .config and lspci output for the system I
> used.
>
> I have also loaded your patch set into OSDL's on-line patch manager.
> The patch stack I used can be found here:
>
> APIC changes:
> http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=1842
>
> i8259 changes:
> http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=1843
>
> reboot on BSP:
> http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=1844
>
> hwfixes & x86kexec:
> http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=1845
>
> For the lazy among us, I have also uploaded a combined patch for 2.5.69
> that includes the four previous patches in one:
> http://www.osdl.org/cgi-bin/plm?module=patch_info&patch_id=1846
And Andrew has it in 2.5.69-mm4 and is busy pestering me about compile
errors. There needs to be an updated version where all of the
appropriate functions have the noreturn attribute. Hopefully
I can do a thorough job this weekend, and create some updated patches.
Eric
next prev parent reply other threads:[~2003-05-14 5:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3EBA626E.6040205@cyberone.com.au>
[not found] ` <20030508121211.532dcbcf.akpm@digeo.com>
[not found] ` <3EBC37C4.9090602@cyberone.com.au>
[not found] ` <20030509162911.2cd5321e.akpm@digeo.com>
[not found] ` <m1u1c37d2o.fsf@frodo.biederman.org>
[not found] ` <20030509201327.734caf9e.akpm@digeo.com>
[not found] ` <m1of2978ao.fsf@frodo.biederman.org>
[not found] ` <20030511121753.7a883afb.akpm@digeo.com>
2003-05-12 0:26 ` Updated kexec diffs Eric W. Biederman
2003-05-13 21:26 ` [KEXEC][2.5.69] " Andy Pfiffer
2003-05-14 5:11 ` Eric W. Biederman [this message]
2003-05-14 5:23 ` Andrew Morton
2003-05-14 12:50 ` Eric W. Biederman
2003-05-14 17:14 ` Andrew Morton
2003-05-14 13:30 ` Rolf Eike Beer
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=m1k7cu3yey.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=akpm@digeo.com \
--cc=andyp@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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