mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joseph Salisbury <joseph.salisbury@canonical.com>
To: tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, dave.hansen@linux.intel.com,
	linux-rt-users@vger.kernel.org
Subject: Issue With real-time patches on 5.15.y
Date: Thu, 5 May 2022 19:18:45 -0400	[thread overview]
Message-ID: <bdb23fe5-51ae-8873-a3d7-85f377877c79@canonical.com> (raw)

Hello,

I ran into a build failure after applying the rt40 real-time patches[0] 
to an Ubuntu 22.04 kernel. The Ubuntu kernel is based on upstream stable 
5.15.y(5.15.34 currently).  I believe this patch is the specific one 
that introduces the build issue: 
0086-locking-Allow-to-include-asm-spinlock_types.h-from-l.patch.

After a bisect, the following commit was identified as the cause for the 
build failure:
b50854eca0e0 ("x86/pkru: Remove useless include")

This commit was added to mainline as of 5.16-rc1 and not Cc'd to stable, 
so it should not exist in 5.15.y.  However, it was purposely added to 
the Ubuntu kernel to enable x86 AMX support[1].

The real-time kernel build failure can be resolved by reverting commit 
b50854eca0e0.  The failure seems to be due to the removal of an include 
of xstate.h from pkru.h and caused spinlock_t to not be defined.  The 
commit would only be reverted for the real-time kernel and not any other 
kernels.  I wanted to see if reverting the commit is the proper 
approach, or if cherry-picking additional commits might be a better 
solution in preparation for additional changes that might be coming in 
the future?

Any suggestions would be greatly appreciated.

Thanks,

Joe


[0] 
https://cdn.kernel.org/pub/linux/kernel/projects/rt/5.15/older/patches-5.15.34-rt40.tar.gz
[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1967750

             reply	other threads:[~2022-05-05 23:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-05 23:18 Joseph Salisbury [this message]
2022-05-05 23:20 ` Joseph Salisbury
2022-05-09 10:14   ` Mike Galbraith
2022-05-10 20:00     ` Joseph Salisbury
2022-05-05 23:35 ` Dave Hansen
2022-05-06 19:15   ` Joseph Salisbury

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=bdb23fe5-51ae-8873-a3d7-85f377877c79@canonical.com \
    --to=joseph.salisbury@canonical.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®