From: Ralf Baechle <ralf@linux-mips.org>
To: "Kevin D. Kissell" <kevink@paralogos.com>
Cc: Linux MIPS Org <linux-mips@linux-mips.org>
Subject: Re: SMTC Patches [0 of 3]
Date: Thu, 2 Oct 2008 10:35:10 +0100 [thread overview]
Message-ID: <20081002093510.GA19177@linux-mips.org> (raw)
In-Reply-To: <48C6DC4C.5040208@paralogos.com>
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
next prev parent reply other threads:[~2008-10-02 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 20:27 SMTC Patches [0 of 3] Kevin D. Kissell
2008-09-11 14:12 ` SMTC Patches [0 of 3] (how about 4) Kevin D. Kissell
2008-10-02 9:35 ` Ralf Baechle [this message]
2008-10-02 16:59 ` SMTC Patches [0 of 3] Kevin D. Kissell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081002093510.GA19177@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=kevink@paralogos.com \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.