[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20070628033947.8c614b55.akpm@linux-foundation.org>
Date: Thu, 28 Jun 2007 03:39:47 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Andi Kleen <ak@...e.de>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
Arjan van de Ven <arjan@...radead.org>,
Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
John Stultz <johnstul@...ibm.com>,
Chris Wright <chrisw@...s-sol.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [patch-mm 00/28] High resolution timer updates and x86_64
support - V3
On Thu, 28 Jun 2007 11:47:04 +0200 Andi Kleen <ak@...e.de> wrote:
> On Thursday 28 June 2007 11:42:33 Andrew Morton wrote:
>
> > > The patch set has been tested in the -hrt and -rt trees for quite a while
> > > and the initial problems have been sorted out. Thanks to the folks from the
> > > PowerTop project for testing and feedback.
> >
> > hrm. Looks like none of your testers have HPET_ID_LEGSUP hardware.
>
> AFAIK it's only on IBM Summit. You have such a box?
Intel Nocona SDV thing. Old.
> > btw, if you want to know why I go on and on about crappy commenting, try to
> > work out from the kernel source code what HPET_ID_LEGSUP is, and why it
> > gets special treatment. It is not possible. This is not maintainable
> > code.
>
> We have a reference somewhere to the HPET spec.
The HPET spec won't tell me why HPET_ID_LEGSUP hpets get a kmalloc in Linux
but the !HPET_ID_LEGSUP ones don't.
-
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