All of lore.kernel.org
 help / color / mirror / Atom feed
From: Franck <vagabon.xyz@gmail.com>
To: "Kevin D. Kissell" <kevink@mips.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
	Ralf Baechle <ralf@linux-mips.org>,
	linux-mips@linux-mips.org
Subject: Re: [PATCH] Add support for 4KS cpu.
Date: Wed, 5 Oct 2005 15:20:59 +0200	[thread overview]
Message-ID: <cda58cb80510050620m693040e0o@mail.gmail.com> (raw)
In-Reply-To: <4343A0FE.9080808@mips.com>

2005/10/5, Kevin D. Kissell <kevink@mips.com>:
> I'm personally not a big believer in security-through-obscurity,
> but there are those, both inside and outside MIPS, who felt that
> the security of SmartMIPS cores would be enhanced if we didn't
> give away all of the details.  As a consequence, we put off
> publishing the nitty-gritty details of SmartMIPS for quite a while.
> I note that we now have the programmers' manual on-line at www.mips.com,
> so I guess I'm implicitly cleared to discuss it in at least that level
> of detail.
>

well, I agree with you on "security-through-obscurity" point. From
outside, I feel like MIPS has a lot of things to _hide_ athough that's
not a good feeling for security systems. Anyways...

> A key element of SmartMIPS that allows for a ~2x speedup for
> crypto codes that rely on extended precision math (RSA, ECC)
> is the combination of an extension to the Hi/Lo accumulator
> (called "ACX") with a special extract-and-reduce instruction
> ("MFLHXU").  If one wants to use that in Linux - or at least,
> if one wants to allow more than one thread to be able to use
> it at a time - one needs to save/restore ACX on the kernel
> stackframe, along with Hi and Lo.
>

Correct. I must at least add this in the patch. I'll do it soon.

Thanks for enlight this.
--
               Franck

  reply	other threads:[~2005-10-05 13:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-04  8:49 [PATCH] Add support for 4KS cpu Franck
2005-10-04 11:34 ` Maciej W. Rozycki
2005-10-04 12:38   ` Kevin D. Kissell
2005-10-04 13:29     ` Maciej W. Rozycki
2005-10-04 13:54       ` Kevin D. Kissell
2005-10-04 15:18         ` Franck
2005-10-04 16:01           ` Maciej W. Rozycki
2005-10-04 17:33             ` Franck
2005-10-05  6:55               ` Franck
2005-10-05 13:22                 ` Maciej W. Rozycki
2005-10-05 18:04                   ` Franck
2005-10-05  7:00     ` Franck
2005-10-05  9:46       ` Kevin D. Kissell
2005-10-05 13:20         ` Franck [this message]
2005-10-04 13:10   ` Franck
2005-10-04 13:54     ` Maciej W. Rozycki
2005-10-04 15:10       ` Franck
2005-10-04 17:11         ` Maciej W. Rozycki
2005-10-04 14:17     ` Ralf Baechle
2005-10-04 14:06 ` Ralf Baechle

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=cda58cb80510050620m693040e0o@mail.gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=kevink@mips.com \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=ralf@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.