[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070508095130.GY3505@sequoia.sous-sol.org>
Date: Tue, 8 May 2007 02:51:30 -0700
From: Chris Wright <chrisw@...s-sol.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Chris Wright <chrisw@...s-sol.org>,
LKML <linux-kernel@...r.kernel.org>,
Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
john stultz <johnstul@...ibm.com>, Ingo Molnar <mingo@...e.hu>,
Arjan van de Ven <arjan@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>, Andi Kleen <ak@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] x86-64 highres/dyntick support
* Thomas Gleixner (tglx@...utronix.de) wrote:
> On Tue, 2007-05-08 at 02:39 -0700, Chris Wright wrote:
>
> > OK, looks very similar all things considered. One thing I didn't do
> > was fix lapic timer calibration (was hoping you'd do that part, and you
> > did ;-) I've noticed that something has changed and I'm seeing irq0
> > handled on cpu3 (4 cpu system), where it used to be on cpu0 as expected.
>
> Strange, irq balancing ?
That's what I was wondering, although i have same setup for 32-bit
and it behaves as expected with cpu0 taking hpet or pit on irq0
and lapic timer picked up on the other 3 cpus.
> > In addition lapic timer is firing there, and I'm seeing a higher
> > interrupt load than I used to. This is the same in your set and mine.
>
> Is irq0 _and_ the lapic timer firing ?
Yes.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists