Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Kevin D. Kissell" <kevink@paralogos.com>
To: linux-mips@linux-mips.org
Subject: Re: [PATCH 0/2] Remove SMTC Support
Date: Tue, 08 Apr 2014 15:49:03 -0700	[thread overview]
Message-ID: <53447CDF.3000902@paralogos.com> (raw)
In-Reply-To: <20140408144436.GT17197@linux-mips.org>

On 04/08/2014 07:44 AM, Ralf Baechle wrote:
> On Tue, Apr 08, 2014 at 11:59:08AM +0100, Markos Chandras wrote:
>
>> This patchset removes the MIPS SMTC support.
> While not really a fix I've applied this to my 3.15 fix branch.  At least
> it will avoid us having to fix it up for 3.15 :-)
>
> That said, SMTC was a remarkable hack and ingenious proof of the MT
> architecture.
Sigh. I was rather proud of it.  If it's being excised (and I don't 
begrudge people the right to deprecate it), I guess it means I can 
unsubscribe from the mailing list, as supporting MT hacks was the main 
reason I hung around at all after leaving MIPS.
> Still a sore spot is CONFIG_MIPS_MT_FPAFF with all its uglyness it
> scatters over the tree, in particular the wrapper around the syscall
> entry point.  I wonder if nowadays with the work that's been done on
> supporting inhomogenous SMP systems (ARM biglittle) there's now a
> better way to handle this sort of issue.
Even at the time, I'd identified a cleaner way to deal with this sort of 
thing, but the maintainer for the code in question wouldn't give me the 
time of day, so I solved the problem as well as the politics of Linux 
allowed.  As I understand it, the MIPS FP Affinity hack still 
outperformed some rather more complex solutions that contemporary 
inhomogeneous (is that different from heterogeneous?) MT machines (e.g. 
Niagara) were using.

/K.

  reply	other threads:[~2014-04-08 22:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08 10:59 [PATCH 0/2] Remove SMTC Support Markos Chandras
2014-04-08 10:59 ` Markos Chandras
2014-04-08 10:59 ` [PATCH 1/2] MIPS: " Markos Chandras
2014-04-08 10:59   ` Markos Chandras
2014-04-08 11:03   ` Markos Chandras
2014-04-08 11:03     ` Markos Chandras
2014-04-08 10:59 ` [PATCH 2/2] MIPS: Kconfig: Make MIPS_MT_SMP a regular Kconfig symbol Markos Chandras
2014-04-08 10:59   ` Markos Chandras
2014-04-08 14:44 ` [PATCH 0/2] Remove SMTC Support Ralf Baechle
2014-04-08 22:49   ` Kevin D. Kissell [this message]
2014-05-05  3:29     ` Maciej W. Rozycki

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=53447CDF.3000902@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox