MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16492.36299.278716.247546@alkaid.it.uu.se>
Date: Thu, 1 Apr 2004 23:46:51 +0200
From: Mikael Pettersson <mikpe@csd.uu.se>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-rc2-mm2
In-Reply-To: <20040401113043.17fe8279.akpm@osdl.org>
References: <20040323232511.1346842a.akpm@osdl.org>
	<16492.7681.332798.230663@alkaid.it.uu.se>
	<20040401113043.17fe8279.akpm@osdl.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1279
Lines: 39

Andrew Morton writes:
 > Mikael Pettersson <mikpe@csd.uu.se> wrote:
 > >
 > > On 23 Mar 2004, Andrew Morton wrote:
 > >  > Changes since 2.6.5-rc2-mm1:
 > > ...
 > >  > -nmi_watchdog-local-apic-fix.patch
 > >  > -nmi-1-hz-2.patch
 > >  > 
 > >  >  I think these were causing kgdb to malfunction.
 > > 
 > > Any concrete evidence about this? I fail to see how
 > > the updated nmi-1-hz patch I wrote could affect kgdb
 > > in a way that wouldn't also happen on UP w/o the patch.
 > > 
 > > IOW, I'm more suspicious about the other patch to
 > > signal LAPIC NMIs on both threads on HT P4.
 > 
 > Which patch is that?

I belive nmi-1-hz-2.patch is Ok. It only changes NMI HZ.
nmi_watchdog-local-apic-fix.patch is a more likely suspect
since it actually changes NMI behaviour.

 > I'll bring the patches back, let them bake for a while.

Please try with just the nmi-1-hz-2.patch for now.

 > Could you take a look at the kgdb stub's MNI usage, see if you can spot any
 > nasty interactions?

I can have a go at it this weekend.

/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/