From: Patrick Robb <probb@iol.unh.edu>
To: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
Cc: Ruifeng Wang <Ruifeng.Wang@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
Dharmik Jayesh Thakkar <DharmikJayesh.Thakkar@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, 29 Aug 2023 20:05:25 -0400 [thread overview]
Message-ID: <CAJvnSUCJ1tqUAwPU4QBwxHohLObDHv6Zzn8dzZ-u-Rb13Q+DYw@mail.gmail.com> (raw)
In-Reply-To: <CAOb5WZZ9eR9JBv825RLo1zqYM0hcD=Fozzqt4m7JeGUeVSO0gA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
Hi Juraj,
Thanks for the guidance. The kernel version in use on the Ampere server
currently is 5.4.0-155-generic. The tags for the 22.04 repo you suggested
only include 5.15 kernel versions, so I can't checkout to the
currently running kernel per your recommendation. I figure the idea behind
checking out to the kernel currently running is to maintain the current
state as much as possible, and ensure the currently running kernel config
could be re-used. If I instead clone the 20.04/focal repo I can checkout to
5.4.0-155, but the diffs you shared do not cleanly apply.
On the other hand, from looking directly at the files on Jammy/5.15[1], it
looks like the qat diffs (https://lkml.org/lkml/2022/6/17/328) have already
reached that kernel version. If indeed applying these diffs is not needed
in this case, is there any reason why I shouldn't just re-build the kernel
from here? I don't want to do this (and necessarily advance the kernel
version from 5.4 to 5.15) without asking you since I don't know what the
negative implications of this action may be, if any.
[1] https://git.launchpad.net/~ubuntu-kernel-stable/+git/jammy/
[-- Attachment #2: Type: text/html, Size: 1424 bytes --]
next prev parent reply other threads:[~2023-08-30 0:05 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 [this message]
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
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=CAJvnSUCJ1tqUAwPU4QBwxHohLObDHv6Zzn8dzZ-u-Rb13Q+DYw@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=DharmikJayesh.Thakkar@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=ci@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=nd@arm.com \
/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).