public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: stable@vger.kernel.org, Denis Nikitin <denik@chromium.org>,
	linux-kernel@vger.kernel.org, patches@lists.linux.dev,
	Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH 5.15.y] KVM: arm64: nvhe: Fix build with profile optimization
Date: Sat, 14 Jan 2023 10:48:57 +0100	[thread overview]
Message-ID: <Y8J6iSOVwGslj3jV@kroah.com> (raw)
In-Reply-To: <20230113002210.3984665-1-swboyd@chromium.org>

On Thu, Jan 12, 2023 at 04:22:10PM -0800, Stephen Boyd wrote:
> From: Denis Nikitin <denik@chromium.org>
> 
> commit bde971a83bbff78561458ded236605a365411b87 upstream.
> 
> Kernel build with clang and KCFLAGS=-fprofile-sample-use=<profile> fails with:
> 
> error: arch/arm64/kvm/hyp/nvhe/kvm_nvhe.tmp.o: Unexpected SHT_REL
> section ".rel.llvm.call-graph-profile"
> 
> Starting from 13.0.0 llvm can generate SHT_REL section, see
> https://reviews.llvm.org/rGca3bdb57fa1ac98b711a735de048c12b5fdd8086.
> gen-hyprel does not support SHT_REL relocation section.
> 
> Filter out profile use flags to fix the build with profile optimization.
> 
> Signed-off-by: Denis Nikitin <denik@chromium.org>
> Signed-off-by: Marc Zyngier <maz@kernel.org>
> Link: https://lore.kernel.org/r/20221014184532.3153551-1-denik@chromium.org
> Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> ---
> 
> I need this to properly compile 5.15.y stable kernels in the chromeos build
> system.

Now queued up, thanks.

greg k-h

      reply	other threads:[~2023-01-14  9:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-13  0:22 [PATCH 5.15.y] KVM: arm64: nvhe: Fix build with profile optimization Stephen Boyd
2023-01-14  9:48 ` Greg KH [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=Y8J6iSOVwGslj3jV@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=denik@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=patches@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --cc=swboyd@chromium.org \
    /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