From: Tom Lendacky <thomas.lendacky@amd.com>
To: Domen Stangar <domen.stangar@gmail.com>, John Allen <john.allen@amd.com>
Cc: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: problem with ccp-crypto module on apu
Date: Wed, 20 Jan 2021 09:25:06 -0600 [thread overview]
Message-ID: <e4b683a5-28d3-ab4e-22eb-6f94e2799ea3@amd.com> (raw)
In-Reply-To: <emf3681a05-10b5-44ad-b516-c8492fdf8f3a@domen-5950x>
On 1/17/21 4:16 AM, Domen Stangar wrote:
> Sorry for late answer, somewhat missed mail.
>
> dmesg last lines that where added
>
> [ 325.691756] ccp 0000:0a:00.2: enabling device (0000 -> 0002)
> [ 325.692217] ccp 0000:0a:00.2: ccp enabled
> [ 325.702401] ccp 0000:0a:00.2: tee enabled
> [ 325.702405] ccp 0000:0a:00.2: psp enabled
>
> /sys/kernel/debug/ccp/ccp-1/stats
> Total Interrupts Handled: 0
> Total Operations: 1
> AES: 0
> XTS AES: 0
> SHA: 0
> SHA: 0
> RSA: 0
> Pass-Thru: 1
> ECC: 0
>
> interrupts output attached.
Ok, the interrupts are not being delivered from the CCP (running in the
AMD Secure Processor or psp) to the x86. This is a BIOS/AGESA issue that
will require a BIOS fix. I don't know what level of AGESA it will be
delivered in and when your BIOS supplier would incorporate it, so my only
suggestion is to not use the ccp and ccp-crypto modules for now.
Thanks,
Tom
>
> Domen
>
> ------ Original Message ------
> From: "John Allen" <john.allen@amd.com>
> To: "Domen Stangar" <domen.stangar@gmail.com>
> Cc: "Tom Lendacky" <thomas.lendacky@amd.com>;
> "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
> Sent: 07/01/2021 17:10:50
> Subject: Re: problem with ccp-crypto module on apu
>
>> On Mon, Jan 04, 2021 at 04:10:26PM +0000, Domen Stangar wrote:
>>> Device name: ccp-1
>>> RNG name: ccp-1-rng
>>> # Queues: 3
>>> # Cmds: 0
>>> Version: 5
>>> Engines: AES 3DES SHA RSA ECC ZDE TRNG
>>> Queues: 5
>>> LSB Entries: 128
>>>
>>> Let me know if you need anything else.
>>
>> Hi Domen,
>>
>> Looks like we may have a lead on this problem.
>>
>> Could you provide the following when you're loading the module?
>>
>> dmesg
>> /proc/interrupts
>> /sys/kernel/debug/ccp/ccp-1/stats
>>
>> Thanks,
>> John
>>
>>> Domen
>>>
>>> > Domen, do you have the debugfs support enabled? Could you supply the
>>> output from /sys/kernel/debug/ccp/ccp-X/info (where X is replaced with
>>> each of the present ccp ordinal values)?
>>> >
>>> > Thanks,
>>> > Tom
>>> >
>>>
next prev parent reply other threads:[~2021-01-20 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <em96a2a8ae-80a7-4608-905e-5d932c0cf9bb@domen1-pc>
2020-12-28 15:22 ` problem with ccp-crypto module on apu John Allen
2021-01-04 14:36 ` Tom Lendacky
2021-01-04 16:10 ` Re[2]: " Domen Stangar
2021-01-07 15:10 ` John Allen
2021-01-17 10:16 ` Re[2]: " Domen Stangar
2021-01-20 15:25 ` Tom Lendacky [this message]
2020-12-17 7:52 Domen Stangar
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=e4b683a5-28d3-ab4e-22eb-6f94e2799ea3@amd.com \
--to=thomas.lendacky@amd.com \
--cc=domen.stangar@gmail.com \
--cc=john.allen@amd.com \
--cc=linux-crypto@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).