Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Guillaume Morin <guillaume@morinfr.org>
To: gregkh@linuxfoundation.org, tglozar@redhat.com,
	stable@vger.kernel.org, bristot@kernel.org, lgoncalv@redhat.com
Subject: 6.6.78: timerlat_{hist,top} fail to build
Date: Wed, 19 Feb 2025 15:40:35 +0100	[thread overview]
Message-ID: <Z7XtY3GRlRcKCAzs@bender.morinfr.org> (raw)

Hello,

The following patches prevent Linux 6.6.78+ rtla to build:

- "rtla/timerlat_top: Set OSNOISE_WORKLOAD for kernel threads" (stable
commit 41955b6c268154f81e34f9b61cf8156eec0730c0)
- "rtla/timerlat_hist: Set OSNOISE_WORKLOAD for kernel threads" (stable
commit 83b74901bdc9b58739193b8ee6989254391b6ba7)

Both were added to Linux 6.6.78 based on the Fixes tag in the upstream
commits.

These patches prevent 6.6.78 rta to build with a similar error (missing
kernel_workload in the params struct)
src/timerlat_top.c:687:52: error: ‘struct timerlat_top_params’ has no member named ‘kernel_workload’

These patches appear to depend on "rtla/timerlat: Make user-space
threads the default" commit fb9e90a67ee9a42779a8ea296a4cf7734258b27d
which is not present in 6.6.

I am not sure if it's better to revert them or pick up
fb9e90a67ee9a42779a8ea296a4cf7734258b27d in 6.6. Tomas, what do you
think?

HTH,

Guillaume.

-- 
Guillaume Morin <guillaume@morinfr.org>

             reply	other threads:[~2025-02-19 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19 14:40 Guillaume Morin [this message]
2025-02-19 15:03 ` 6.6.78: timerlat_{hist,top} fail to build Tomas Glozar
2025-02-20 14:03   ` Guillaume Morin
2025-02-20 14:26     ` Greg KH

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=Z7XtY3GRlRcKCAzs@bender.morinfr.org \
    --to=guillaume@morinfr.org \
    --cc=bristot@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lgoncalv@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=tglozar@redhat.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