.. | .. |
---|
4 | 4 | Contact: Kent Yoder <key@linux.vnet.ibm.com> |
---|
5 | 5 | Description: |
---|
6 | 6 | |
---|
7 | | - These debugfs interfaces are built by the nx-crypto driver, built in |
---|
| 7 | +These debugfs interfaces are built by the nx-crypto driver, built in |
---|
8 | 8 | arch/powerpc/crypto/nx. |
---|
9 | 9 | |
---|
10 | 10 | Error Detection |
---|
11 | 11 | =============== |
---|
12 | 12 | |
---|
13 | 13 | errors: |
---|
14 | | -- A u32 providing a total count of errors since the driver was loaded. The |
---|
15 | | -only errors counted here are those returned from the hcall, H_COP_OP. |
---|
| 14 | + A u32 providing a total count of errors since the driver was loaded. The |
---|
| 15 | + only errors counted here are those returned from the hcall, H_COP_OP. |
---|
16 | 16 | |
---|
17 | 17 | last_error: |
---|
18 | | -- The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not |
---|
19 | | -recorded here (the hcall will retry until -EBUSY goes away). |
---|
| 18 | + The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not |
---|
| 19 | + recorded here (the hcall will retry until -EBUSY goes away). |
---|
20 | 20 | |
---|
21 | 21 | last_error_pid: |
---|
22 | | -- The process ID of the process who received the most recent error from the |
---|
23 | | -hcall. |
---|
| 22 | + The process ID of the process who received the most recent error from the |
---|
| 23 | + hcall. |
---|
24 | 24 | |
---|
25 | 25 | Device Use |
---|
26 | 26 | ========== |
---|
27 | 27 | |
---|
28 | 28 | aes_bytes: |
---|
29 | | -- The total number of bytes encrypted using AES in any of the driver's |
---|
30 | | -supported modes. |
---|
| 29 | + The total number of bytes encrypted using AES in any of the driver's |
---|
| 30 | + supported modes. |
---|
31 | 31 | |
---|
32 | 32 | aes_ops: |
---|
33 | | -- The total number of AES operations submitted to the hardware. |
---|
| 33 | + The total number of AES operations submitted to the hardware. |
---|
34 | 34 | |
---|
35 | 35 | sha256_bytes: |
---|
36 | | -- The total number of bytes hashed by the hardware using SHA-256. |
---|
| 36 | + The total number of bytes hashed by the hardware using SHA-256. |
---|
37 | 37 | |
---|
38 | 38 | sha256_ops: |
---|
39 | | -- The total number of SHA-256 operations submitted to the hardware. |
---|
| 39 | + The total number of SHA-256 operations submitted to the hardware. |
---|
40 | 40 | |
---|
41 | 41 | sha512_bytes: |
---|
42 | | -- The total number of bytes hashed by the hardware using SHA-512. |
---|
| 42 | + The total number of bytes hashed by the hardware using SHA-512. |
---|
43 | 43 | |
---|
44 | 44 | sha512_ops: |
---|
45 | | -- The total number of SHA-512 operations submitted to the hardware. |
---|
| 45 | + The total number of SHA-512 operations submitted to the hardware. |
---|