mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Nathan Chancellor <nathan@kernel.org>,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org, "anup@brainfault.org" <anup@brainfault.org>
Subject: Re: [GIT PULL] First batch of KVM changes for Linux 6.13 merge window
Date: Thu, 21 Nov 2024 19:19:33 +0100	[thread overview]
Message-ID: <d4048dc8-b740-47f6-8e1e-258441eb77d1@redhat.com> (raw)
In-Reply-To: <Zz9E8lYTsfrMjROi@sashalap>

On 11/21/24 15:34, Sasha Levin wrote:
> On Thu, Nov 21, 2024 at 03:07:03PM +0100, Paolo Bonzini wrote:
>> On 11/21/24 14:26, Nathan Chancellor wrote:
>>> 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:
>>>>
>>>> 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().
>>
>> Thanks Sasha. :(  Looks like Stephen does not build for risc-v.
> 
> He does :)
>
> This issue was reported[1] about a week ago in linux-next

Yeah, that's Linaro not Stephen.

> and a fix was
> sent out (the one you linked to be used for conflict resolution), but it
> looks like it wasn't picked up by either the perf tree or the KVM tree.

Yeah, that's not surprising. :(  Neither KVM nor I weren't CC'd on 
either the report or the bugfix; and the perf tree didn't have the code 
at all as Ingo pointed out 
(https://lore.kernel.org/all/ZzxDvLKGz1ouWzgX@gmail.com/).  Anup was 
CC'd on the bugfix but he must have missed too and didn't notify me.

Paolo


  reply	other threads:[~2024-11-21 18:19 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
2024-11-21 14:07     ` Paolo Bonzini
2024-11-21 14:34       ` Sasha Levin
2024-11-21 18:19         ` Paolo Bonzini [this message]
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=d4048dc8-b740-47f6-8e1e-258441eb77d1@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=anup@brainfault.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathan@kernel.org \
    --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®