From: "Kevin D. Kissell" <kevink@paralogos.com>
To: Linux MIPS Org <linux-mips@linux-mips.org>
Subject: SMTC Patches [0 of 3]
Date: Tue, 09 Sep 2008 22:27:56 +0200 [thread overview]
Message-ID: <48C6DC4C.5040208@paralogos.com> (raw)
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.
Regards,
Kevin K.
next reply other threads:[~2008-09-09 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 20:27 Kevin D. Kissell [this message]
2008-09-11 14:12 ` SMTC Patches [0 of 3] (how about 4) Kevin D. Kissell
2008-10-02 9:35 ` SMTC Patches [0 of 3] Ralf Baechle
2008-10-02 16:59 ` 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=48C6DC4C.5040208@paralogos.com \
--to=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.