Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Kienan Stewart via lttng-dev <lttng-dev@lists.lttng.org>
To: Jean-Marc Chevalier <jean-marc.chevalier@polymtl.ca>,
	"lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: Re: lttng-modules-2.13.18 Condition for Kernel 5.14.0-582.el9.x86_64 of Centos Stream 9.
Date: Wed, 14 May 2025 15:57:38 -0400	[thread overview]
Message-ID: <7b925d07-87b9-4d64-87c4-6f787b8e2856@efficios.com> (raw)
In-Reply-To: <YT3PR01MB6421C77EF52F3D7A62651E93DC91A@YT3PR01MB6421.CANPRD01.PROD.OUTLOOK.COM>

Hi Jean-Marc,

On 5/14/25 3:16 PM, Jean-Marc Chevalier via lttng-dev wrote:
> For lttng-modules-2.13.18
> 
> I have this error with kernel version 5.14.0-582.el9.x86_64:
> 
> lttng-modules-2.13.18/src/lttng-statedump-impl.c:415:20: error: 'dev_base_lock' undeclared (first use in this function); did you mean 'device_lock'?
> 
> I got it to create modules by changing the condition on line 396
> 
> Original:
> #if (LTTNG_LINUX_VERSION_CODE >= LTTNG_KERNEL_VERSION(6,9,0))
> 
> Modification:
> #if (LTTNG_LINUX_VERSION_CODE >= LTTNG_KERNEL_VERSION(6,9,0)) || (LTTNG_LINUX_VERSION_CODE == LTTNG_KERNEL_VERSION(5,14,0))
> 
> I don't know how you distinguish the version after the dash character for RHEL kernels.
> 

For RHEL kernels you can use the LTTNG_RHEL_KERNEL_RANGE macro. E.g.

```
LTTNG_RHEL_KERNEL_RANGE(5,14,0,503,21,1,  5,15,0,0,0,0))
```

thanks,
kienan

> - JM
> 
> --
> - Jean-Marc Chevalier
>    Technicien
>    Génie informatique Génie logiciel
>    Local:     M-4002
>    Téléphone: 514-340-4711 x4266
> 


      reply	other threads:[~2025-05-14 19:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-14 19:16 Jean-Marc Chevalier via lttng-dev
2025-05-14 19:57 ` Kienan Stewart via lttng-dev [this message]

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=7b925d07-87b9-4d64-87c4-6f787b8e2856@efficios.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=jean-marc.chevalier@polymtl.ca \
    --cc=kstewart@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox