From: ebiederm@xmission.com (Eric W. Biederman)
To: Kasper Dupont <kasperd@daimi.au.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [CFT] kexec syscall for 2.5.43 (linux booting linux)
Date: 28 Oct 2002 01:24:02 -0700 [thread overview]
Message-ID: <m1hef7j7j1.fsf@frodo.biederman.org> (raw)
In-Reply-To: <3DBCEB2E.BC3956FD@daimi.au.dk>
Kasper Dupont <kasperd@daimi.au.dk> writes:
> "Eric W. Biederman" wrote:
> >
> > +static void i8259A_remove(struct device *dev)
> > +{
> > + /* Restore the i8259A to it's legacy dos setup.
> > + * The kernel won't be using it any more, and it
> > + * just might make reboots, and kexec type applications
> > + * more stable.
> > + */
> > + outb(0xff, 0x21); /* mask all of 8259A-1 */
> > + outb(0xff, 0xA1); /* mask all of 8259A-1 */
> > +
> > + outb_p(0x11, 0x20); /* ICW1: select 8259A-1 init */
> > + outb_p(0x08, 0x21); /* ICW2: 8259A-1 IR0-7 mappend to 0x8-0xf */
> > + outb_p(0x01, 0x21); /* Normal 8086 auto EOI mode */
> > +
> > + outb_p(0x11, 0xA0); /* ICW1: select 8259A-2 init */
> > + outb_p(0x08, 0xA1); /* ICW2: 8259A-2 IR0-7 mappend to 0x70-0x77 */
>
> ^^^^ ^^^^
>
> This looks wrong to me.
Thanks that was a clear cut and paste bug.
I am in the process of moving the i8259A setup code into my kexec user
space program. I believe it is inappropriate to assume the interrupt
controller is going to be used by dos when it is shut down. So my
latest version (just published) simply masks all interrupts through
the pic.
The pic setup code I am in the process of moving into kexec-tools, and
since the pic is well know I will do this piece of setup work
there.
Another bug worth noting in this code, is that as of 2.5.44 only the
->shutdown methods are called on reboot and not the ->remove methods
so I actually hooked the wrong routine. Just in case someone else is
trying to hook that moving target.
Eric
next prev parent reply other threads:[~2002-10-28 8:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 19:59 [CFT] kexec syscall for 2.5.43 (linux booting linux) Eric W. Biederman
[not found] ` <20021018173248.E14894@almesberger.net>
[not found] ` <m1bs5rz1d6.fsf@frodo.biederman.org>
[not found] ` <20021018231540.C7951@almesberger.net>
[not found] ` <20021019025309.A24579@almesberger.net>
[not found] ` <m17kgfyltc.fsf@frodo.biederman.org>
[not found] ` <20021019040600.D7951@almesberger.net>
2002-10-19 9:34 ` Eric W. Biederman
2002-10-19 17:18 ` Werner Almesberger
2002-10-19 17:37 ` Eric W. Biederman
2002-10-21 23:11 ` [Fastboot] " Andy Pfiffer
2002-10-22 4:18 ` Eric W. Biederman
2002-10-22 6:04 ` Eric W. Biederman
2002-10-22 8:33 ` Eric W. Biederman
2002-10-22 3:57 ` Rob Landley
2002-10-22 14:48 ` Eric W. Biederman
2002-10-22 16:02 ` Eric W. Biederman
2002-10-22 16:27 ` erich
2002-10-23 2:23 ` Eric W. Biederman
2002-10-22 16:30 ` erich
2002-10-22 23:27 ` Andy Pfiffer
2002-10-22 23:32 ` Andy Pfiffer
2002-10-22 8:30 ` Werner Almesberger
2002-10-22 8:55 ` Eric W. Biederman
2002-10-22 23:17 ` Andy Pfiffer
2002-10-23 6:29 ` Eric W. Biederman
2002-10-23 17:11 ` Andy Pfiffer
2002-10-24 17:10 ` Eric W. Biederman
2002-10-28 7:45 ` Kasper Dupont
2002-10-28 8:24 ` Eric W. Biederman [this message]
2002-10-28 8:48 ` Kasper Dupont
2002-10-28 17:14 ` Eric W. Biederman
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=m1hef7j7j1.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=kasperd@daimi.au.dk \
--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