mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Sasha Levin <sashal@kernel.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org
Subject: Re: [GIT PULL] First batch of KVM changes for Linux 6.13 merge window
Date: Thu, 21 Nov 2024 06:26:08 -0700	[thread overview]
Message-ID: <20241121132608.GA4113699@thelio-3990X> (raw)
In-Reply-To: <Zz8t95SNFqOjFEHe@sashalap>

On Thu, Nov 21, 2024 at 07:56:23AM -0500, Sasha Levin wrote:
> Hi Paolo,
> 
> On Wed, Nov 20, 2024 at 08:58:42AM -0500, Paolo Bonzini wrote:
> >      riscv: perf: add guest vs host distinction
> 
> When merging this PR into linus-next, I've started seeing build errors:
> 
> In file included from /builds/linux/arch/riscv/kernel/asm-offsets.c:12:
> In file included from /builds/linux/arch/riscv/include/asm/kvm_host.h:23:
> In file included from /builds/linux/arch/riscv/include/asm/kvm_vcpu_pmu.h:12:
> In file included from /builds/linux/include/linux/perf/riscv_pmu.h:12:
> /builds/linux/include/linux/perf_event.h:1679:64: error: too many arguments provided to function-like macro invocation
>  1679 | extern unsigned long perf_misc_flags(struct perf_event *event, struct pt_regs *regs);
>       |                                                                ^
> /builds/linux/arch/riscv/include/asm/perf_event.h:15:9: note: macro 'perf_misc_flags' defined here
>    15 | #define perf_misc_flags(regs) perf_misc_flags(regs)
>       |         ^
> 
> Looks like this is due to 2c47e7a74f44 ("perf/core: Correct perf
> sampling with guest VMs") which went in couple of days ago through
> Ingo's perf tree and changed the number of parameters for
> perf_misc_flags().

There is a patch out to fix this but it seems like it needs to be
applied during this merge?

https://lore.kernel.org/20241116160506.5324-1-prabhakar.mahadev-lad.rj@bp.renesas.com/
https://lore.kernel.org/ZzxDvLKGz1ouWzgX@gmail.com/

Cheers,
Nathan

  reply	other threads:[~2024-11-21 13:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20 13:58 Paolo Bonzini
2024-11-21 12:56 ` Sasha Levin
2024-11-21 13:26   ` Nathan Chancellor [this message]
2024-11-21 14:07     ` Paolo Bonzini
2024-11-21 14:34       ` Sasha Levin
2024-11-21 18:19         ` Paolo Bonzini
2024-11-22  4:40           ` Anup Patel
2024-11-24  0:34 ` pr-tracker-bot

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=20241121132608.GA4113699@thelio-3990X \
    --to=nathan@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sashal@kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®