From: Ruifeng Wang <Ruifeng.Wang@arm.com>
To: "Patrick Robb" <probb@iol.unh.edu>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>
Cc: Dharmik Jayesh Thakkar <DharmikJayesh.Thakkar@arm.com>,
David Marchand <david.marchand@redhat.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"ci@dpdk.org" <ci@dpdk.org>, nd <nd@arm.com>
Subject: Re: Intel QAT 8970 accel card on ARM Ampere Server
Date: Tue, 14 Nov 2023 07:34:38 +0000 [thread overview]
Message-ID: <AS8PR08MB7080E48001CD0368EA45D1A69EB2A@AS8PR08MB7080.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAJvnSUB1Wns-Ub3zNyUWotipZ2f23jF=NQxUS6v8_b8W9kNCQg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]
Hi Patrick,
It seems kernel v5.15 has a defect on this. A similar issue was fixed by commit:
40da865381ad ("crypto: qat - remove unneeded packed attribute")
Could you patch the kernel and try again?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=40da865381ad061ab75a7a9da469ed4e623bdfeb
Thanks,
Ruifeng
From: Patrick Robb <probb@iol.unh.edu>
Date: Friday, November 3, 2023 at 6:01 AM
To: Juraj Linkeš <juraj.linkes@pantheon.tech>
Cc: Dharmik Jayesh Thakkar <DharmikJayesh.Thakkar@arm.com>, David Marchand <david.marchand@redhat.com>, Ruifeng Wang <Ruifeng.Wang@arm.com>, Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>, ci@dpdk.org <ci@dpdk.org>, nd <nd@arm.com>
Subject: Re: Intel QAT 8970 accel card on ARM Ampere Server
On Wed, Oct 11, 2023 at 4:13 PM Patrick Robb <probb@iol.unh.edu<mailto:probb@iol.unh.edu>> wrote:
root@arm-ampere-dut:~# echo 16 > /sys/bus/pci/drivers/c6xx/0000:03:00.0/sriov_numvfs
Segmentation fault (core dumped)
Hi Aaron,
Thanks for offering to take a look. I'm not sure if you've seen the rest of this conversation already from it being on the ci mailing list or not, but modinfo looks good for qat_c62x andqat_c62xvf after the custom kernel was built. From there, it should be possible to bind some VFs for each PF on the QAT card, per documentation here https://doc.dpdk.org/guides/cryptodevs/qat.html but it results in a seg fault like you see above. Let me know if you have any ideas.
[-- Attachment #2: Type: text/html, Size: 5386 bytes --]
next prev parent reply other threads:[~2023-11-14 7:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 17:13 Patrick Robb
2023-08-04 9:48 ` Ruifeng Wang
2023-08-08 7:07 ` Juraj Linkeš
2023-08-08 7:11 ` Ruifeng Wang
2023-08-11 21:18 ` Patrick Robb
2023-08-21 8:45 ` Juraj Linkeš
2023-08-30 0:05 ` Patrick Robb
2023-09-01 21:30 ` Patrick Robb
2023-09-11 8:13 ` Juraj Linkeš
2023-09-20 18:28 ` Patrick Robb
2023-09-25 15:19 ` Ruifeng Wang
2023-10-09 16:34 ` Patrick Robb
2023-10-10 2:28 ` Patrick Robb
2023-10-10 3:55 ` Dharmik Jayesh Thakkar
2023-10-10 7:25 ` David Marchand
2023-10-10 15:03 ` Dharmik Jayesh Thakkar
2023-10-10 15:12 ` David Marchand
2023-10-10 15:59 ` Patrick Robb
2023-10-10 21:50 ` Dharmik Jayesh Thakkar
2023-10-11 8:14 ` Juraj Linkeš
2023-10-11 20:13 ` Patrick Robb
2023-11-02 22:00 ` Patrick Robb
2023-11-14 7:34 ` Ruifeng Wang [this message]
2023-11-14 14:36 ` Patrick Robb
2024-02-27 6:58 ` Patrick Robb
2024-02-27 13:50 ` Honnappa Nagarahalli
2024-02-28 20:00 ` Patrick Robb
2024-02-28 20:40 ` Honnappa Nagarahalli
2024-03-07 5:27 ` Patrick Robb
2024-03-07 7:56 ` David Marchand
2023-10-11 11:51 ` David Marchand
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=AS8PR08MB7080E48001CD0368EA45D1A69EB2A@AS8PR08MB7080.eurprd08.prod.outlook.com \
--to=ruifeng.wang@arm.com \
--cc=DharmikJayesh.Thakkar@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=ci@dpdk.org \
--cc=david.marchand@redhat.com \
--cc=juraj.linkes@pantheon.tech \
--cc=nd@arm.com \
--cc=probb@iol.unh.edu \
/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).