linux-mips
[Top] [All Lists]

Re: SMTC Patches [0 of 3]

To: "Kevin D. Kissell" <kevink@paralogos.com>
Subject: Re: SMTC Patches [0 of 3]
From: Ralf Baechle <ralf@linux-mips.org>
Date: Thu, 2 Oct 2008 10:35:10 +0100
Cc: Linux MIPS Org <linux-mips@linux-mips.org>
In-reply-to: <48C6DC4C.5040208@paralogos.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <48C6DC4C.5040208@paralogos.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.18 (2008-05-17)
On Tue, Sep 09, 2008 at 10:27:56PM +0200, Kevin D. Kissell wrote:
> From: "Kevin D. Kissell" <kevink@paralogos.com>
> Date: Tue, 09 Sep 2008 22:27:56 +0200
> To: Linux MIPS Org <linux-mips@linux-mips.org>
> Subject: SMTC Patches [0 of 3]
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> 
> I've managed to steal enough time to rework the SMTC support
> for the MIPS 34K (and, I suppose 1004K) processors so that it
> works again near the head of the source tree.  This involved
> a complete rework of the clocking model to be compatible with
> new common timing event system, which finally enables "tickless"
> operation in SMTC, something it needed pretty badly.  I also
> solved the problem with using the "wait_irqoff" idle loop
> under SMTC.
>
> There are going to be three patches that will follow.  The
> first two are relatively localized fixes to problems with
> FPU affinity and with IPI replay that I came across in testing
> the new code.  The last is a pretty big patch, but it all
> pretty much hangs together and I couldn't see any sensible
> way to partition it.

I've folded patch 4/3 into 1/3 and backported everything, as far as
it seemed sensible.  One nit was that 2/3 breaks the build and 3/3 fixes
it again.  This sort of build breakage is not uncommon but frowned
uppon these days since it makes use of git bisect for debugging
impossible.

Thanks,

  Ralf

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