Linux cryptographic layer development
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: avi@redhat.com
Cc: ying.huang@intel.com, akpm@linux-foundation.org,
	herbert@gondor.apana.org.au, linux-kernel@vger.kernel.org,
	linux-crypto@vger.kernel.org
Subject: Re: [BUGFIX] Fix AES-NI CTR optimization compiling failure with gas 2.16.1
Date: Fri, 12 Mar 2010 00:42:02 -0800 (PST)	[thread overview]
Message-ID: <20100312.004202.27822414.davem@davemloft.net> (raw)
In-Reply-To: <4B99FD4D.4090206@redhat.com>

From: Avi Kivity <avi@redhat.com>
Date: Fri, 12 Mar 2010 10:37:33 +0200

> Eventually you'll port the entire assembler into macros, as
> instructions are introduced more frequently that people upgrade their
> assemblers.  Maybe we should disable the new features and warn people
> (and distros) to upgrade their tools instead.

I totally and completely disagree.

It would have taken more than a year to get Niagara cpu support out to
people if I had done what you are suggesting.

And here we're talking about one instruction in one specialized case
in a very piece of crypto module assembler.

  reply	other threads:[~2010-03-12  8:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12  7:01 [BUGFIX] Fix AES-NI CTR optimization compiling failure with gas 2.16.1 Huang Ying
2010-03-12  8:37 ` Avi Kivity
2010-03-12  8:42   ` David Miller [this message]
2010-03-12  8:44     ` Avi Kivity
2010-03-12  8:50       ` David Miller
2010-03-12  9:33         ` Avi Kivity
2010-03-13  8:29 ` Herbert Xu
2010-03-23 21:23 ` Andrew Morton
2010-03-24  6:24   ` Huang Ying
2010-03-24 10:51     ` Andrew Morton
2010-03-24 13:38     ` Herbert Xu

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=20100312.004202.27822414.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akpm@linux-foundation.org \
    --cc=avi@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ying.huang@intel.com \
    /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