public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Paul Mackerras <paulus@samba.org>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: AES assembler optimizations
Date: Tue, 10 Aug 2004 18:25:43 -0700	[thread overview]
Message-ID: <20040810182543.064c4bc5.davem@redhat.com> (raw)
In-Reply-To: <16665.28728.720742.251546@cargo.ozlabs.ibm.com>

On Wed, 11 Aug 2004 11:02:48 +1000
Paul Mackerras <paulus@samba.org> wrote:

> David S. Miller writes:
> 
> > On sparc64, we:
> > 
> > 1) Always save the full FPU state at context switch time if it
> >    is active.
> > 
> > 2) On entry to a FPU-using kernel routine, we save the FPU if
> >    it is active.
> 
> How is that implemented?  Do you have some magic to make gcc emit a
> call to an fpu-save routine in the prolog if the function uses the
> FPU?  Or are you only talking about functions written in assembler?

All FPU usage is explicit, and VISEntry (if using the full FPU register
set) or VISEntryHalf (if using only the lower 32 registers) calls
are made to enter an FPU usage area, and VISExit/VISExitHalf is invoked
afterwards.

We could do it with traps, but there is no reason when we know
exactly where these places are and the save code is only a
handful of instructions.


  reply	other threads:[~2004-08-11  1:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2riR3-7U5-3@gated-at.bofh.it>
2004-08-09 14:28 ` AES assembler optimizations Andi Kleen
2004-08-09 16:02   ` Bob Deblier
2004-08-09 17:12     ` Matti Aarnio
2004-08-10 19:51       ` H. Peter Anvin
2004-08-10 20:36         ` David S. Miller
2004-08-11  1:02           ` Paul Mackerras
2004-08-11  1:25             ` David S. Miller [this message]
2004-08-12 20:18           ` Bill Davidsen
2004-08-09 18:16     ` Andi Kleen
2004-08-09 20:20     ` dean gaudet
2004-08-09 13:47 Bob Deblier
2004-08-09 14:32 ` Patrick McFarland

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=20040810182543.064c4bc5.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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