mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harald Welte <HaraldWelte@viatech.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
	Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
Subject: Re: [patch 0/3] crypto: padlock-aes: enable on VIA Nano
Date: Wed, 10 Jun 2009 02:45:52 +0800	[thread overview]
Message-ID: <20090609184552.GL5304@prithivi.gnumonks.org> (raw)
In-Reply-To: <20090609103533.0c334594@dhcp-100-2-144.bos.redhat.com>

On Tue, Jun 09, 2009 at 10:35:33AM -0400, Chuck Ebbert wrote:
> The VIA Nano has a bug that makes the padlock unit fetch extra data
> during encryption operations. Add workarounds for that, and enable
> the driver on x86_64.

Thanks!

Where did you get the errata from, and what kind of document / revision is it?
I have not seen that document so far.

I've asked Centaur to confirm the errata, also inquired whether there will be
a microcode update or a new stepping to fix it.  If yes, we should add proper
checks to the workaround to make sure it's only enabled when we need it.

Out of curiosity: Only the ACE (crypto) is affected, not PHE (hashing)?

I'll also put on my todo list to do some actual benchmarking to determine
how much impact this bug has.  I expect especially for storage encryption,
many crypto operations will be page aligned and thus need the extra memcpy :(

p.s.: the patch to enable padlock on x86_64 is already in the crypto-dev tree,
as far as I know.  Interestingly, I have not observed this problem so far,
despite running dm-crypt on a nano for quite some time. 

Cheers,
-- 
- Harald Welte <HaraldWelte@viatech.com>	    http://linux.via.com.tw/
============================================================================
VIA Free and Open Source Software Liaison

      parent reply	other threads:[~2009-06-09 18:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 14:35 Chuck Ebbert
2009-06-09 14:36 ` [patch 1/3] crypto: padlock-aes: work around Nano CPU errata in ECB mode Chuck Ebbert
2009-06-09 14:37 ` [patch 2/3] crypto: padlock-aes: work around Nano CPU errata in CBC mode Chuck Ebbert
2009-06-09 14:39 ` [patch 3/3] crypto: padlock-aes: enable on 64-bit kernels Chuck Ebbert
2009-06-09 18:47   ` Sebastian Andrzej Siewior
2009-06-09 16:29 ` [patch 0/3] crypto: padlock-aes: enable on VIA Nano Chuck Ebbert
2009-06-09 18:42 ` Sebastian Andrzej Siewior
2009-06-10 16:48   ` Harald Welte
2009-06-09 18:45 ` Harald Welte [this message]

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=20090609184552.GL5304@prithivi.gnumonks.org \
    --to=haraldwelte@viatech.com \
    --cc=cebbert@redhat.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sebastian@breakpoint.cc \
    /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

all inboxes | Powered by JetHome®