From: "Jordan Crouse" <jordan.crouse@amd.com>
To: "Herbert Xu" <herbert@gondor.apana.org.au>
Cc: johnpol@2ka.mipt.ru, mschiller@tdt.de, linux-crypto@vger.kernel.org
Subject: Re: Testing the geode-aes driver with the tcrypt module completely freezes the machine
Date: Thu, 3 May 2007 08:47:44 -0600 [thread overview]
Message-ID: <20070503144744.GA9691@cosmic.amd.com> (raw)
In-Reply-To: <E1Hjbgd-000086-00@gondolin.me.apana.org.au>
On 03/05/07 23:49 +1000, Herbert Xu wrote:
> Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
> >
> > Hm, driver does not perform encryption in-place at all.
> > Since we did not hear from AMD quite for a while, could you please
> > remove src==dst check in geode_aes_crypt() and run tests again.
> > If it is software protection against hardware bug, I doubt such hardware
> > should be used at all...
>
> I agree. Jordan, could you please see if this can be fixed up?
On older versions of the chip, in-place encryption was not possible, even
though there was no hardware protection against it. I can't remember
if the newer chip version can handle in place encryption or not.
I missed out on the context of this thread - does the tcrypt demand
in-place encryption?
Jordan
--
Jordan Crouse
Senior Linux Engineer
Advanced Micro Devices, Inc.
<www.amd.com/embeddedprocessors>
next prev parent reply other threads:[~2007-05-03 14:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 13:12 Testing the geode-aes driver with the tcrypt module completely freezes the machine Martin Schiller
2007-05-03 13:23 ` Evgeniy Polyakov
2007-05-03 13:49 ` Herbert Xu
2007-05-03 14:47 ` Jordan Crouse [this message]
2007-05-03 16:53 ` Evgeniy Polyakov
2007-05-03 14:08 ` Martin Schiller
2007-05-03 14:47 ` Evgeniy Polyakov
-- strict thread matches above, loose matches on Subject: below --
2007-04-26 9:04 Martin Schiller
2007-04-26 11:05 ` Sebastian Siewior
2007-04-26 11:27 ` Martin Schiller
2007-04-27 8:10 ` Herbert Xu
2007-04-27 9:50 ` Evgeniy Polyakov
2007-04-27 9:53 ` Evgeniy Polyakov
2007-05-03 6:19 ` Martin Schiller
2007-05-03 7:57 ` Evgeniy Polyakov
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=20070503144744.GA9691@cosmic.amd.com \
--to=jordan.crouse@amd.com \
--cc=herbert@gondor.apana.org.au \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-crypto@vger.kernel.org \
--cc=mschiller@tdt.de \
/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.