From: Michael Jeanson via lttng-dev <lttng-dev@lists.lttng.org>
To: Martin Hicks <martin@sr-research.com>, lttng-dev@lists.lttng.org
Subject: Re: [lttng-dev] [PATCH] Compile fixes for RHEL 9.3 kernels
Date: Tue, 6 Feb 2024 14:14:14 -0500 [thread overview]
Message-ID: <4a3fa41f-9a61-4c16-a387-c6b996211b8d@efficios.com> (raw)
In-Reply-To: <20240126171833.cppkzs4pl2f4scf6@newton>
On 2024-01-26 12:18, Martin Hicks via lttng-dev wrote:
>
> I'm not sure when some of these changes were backported, but the
> unmodified lttng-modules compiles vs. 5.14.0-162.23.1
>
> This disables the kmem and compaction modules. I don't believe getting
> these to compile will be easy, as the required struct declarations are
> in vmlinux.h, and haven't been moved into mm/internal.h and mm/slab.h in
> the RHEL sources.
>
> Signed-off-by: Martin Hicks <martin@sr-research.com>
Hi Martin,
I tested your patch and did some minor fixes, I added the base kernel version
to the RHEL ABI version check in the Kbuild file because the ABI is tied to a
specific kernel version and it would conflict with other RHEL versions. I also
adjusted the range for 'kfree_skb' to build on RHEL9.2 kernels.
I uploaded the updated patch [1] to our gerrit instance for easier tracking on
our side. Can you please test this version on your system?
You can get the patch using these commands:
git fetch https://review.lttng.org/lttng-modules refs/changes/50/11750/3
git cherry-pick FETCH_HEAD
Thanks,
Michael
[1] https://review.lttng.org/c/lttng-modules/+/11750
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
next prev parent reply other threads:[~2024-02-06 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 17:18 [lttng-dev] [PATCH] Compile fixes for RHEL 9.3 kernels Martin Hicks via lttng-dev
2024-02-06 19:14 ` Michael Jeanson via lttng-dev [this message]
2024-02-07 14:15 ` Martin Hicks via lttng-dev
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=4a3fa41f-9a61-4c16-a387-c6b996211b8d@efficios.com \
--to=lttng-dev@lists.lttng.org \
--cc=martin@sr-research.com \
--cc=mjeanson@efficios.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 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.