lkcd
[Top] [All Lists]

Re: Your patch to stop scheduling during dump

To: bsuparna@xxxxxxxxxx
Subject: Re: Your patch to stop scheduling during dump
From: "Matt D. Robinson" <yakker@xxxxxxxxxxxxxx>
Date: Wed, 13 Jun 2001 09:28:03 -0700
Cc: lkcd@xxxxxxxxxxx, yakker@xxxxxxxxxxxxxx
Organization: Alacritech, Inc.
References: <CA256A6A.00278151.00@xxxxxxxxxxxxxxxxxxx>
Sender: owner-lkcd@xxxxxxxxxxx
bsuparna@xxxxxxxxxx wrote:
> 
> Matt,
> 
> Oops, I'd missed going through the note you'd sent to Michael with the
> patch.
> Found it now.
> 
> Regards
> Suparna

This will only correct the case where scheduling is called during
an interrupt.  I have a 2.4.2 patch that will correct that problem
as well as the dump interrupts case.  If you'd like to give that
a shot (or anyone), let me know.  I've been working with this for
the last two evenings, with some small success.  Larry Sendlosky
also provided a patch for changing when we flush the TLBs, along with
what we do for disable_local_APIC().  I have to incorporate those
changes as well (thanks, Larry).  The other good thing to do is to
add in 'int dump_cpu', to indicate which CPU is dumping.

It's basically the disabling of the local APIC, but I decided to
move all of this into arch/i386/kernel/vmdump.c, instead of
depending on arch/i386/kernel/{traps,smp}.c for stuff.

I guess one thing we need to also do is to create some sort of
GKHI mechanism for allowing people to get a dump and continue
normal operation.

Suparna, do you (and the rest of the IBM folks) need write access
to the SourceForge tree?

--Matt

<Prev in Thread] Current Thread [Next in Thread>