From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: 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.2
Date: Mon, 12 Dec 2022 21:41:55 +0100 [thread overview]
Message-ID: <6d96a62e-d5a1-e606-3bd2-c38f4a6c8545@redhat.com> (raw)
In-Reply-To: <Y5ddb+tGS7phN1vc@google.com>
On 12/12/22 17:57, Sean Christopherson wrote:
> On Mon, Dec 12, 2022, Paolo Bonzini wrote:
>> Linus,
>>
>> The following changes since commit 8332f0ed4f187c7b700831bd7cc83ce180a944b9:
>>
>> KVM: Update gfn_to_pfn_cache khva when it moves within the same page (2022-11-23 18:58:46 -0500)
>>
>> are available in the Git repository at:
>>
>> https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
>>
>> for you to fetch changes up to 1396763d469a83c5d791fa84df7dd17eba83dcf2:
>>
>> Merge remote-tracking branch 'kvm/queue' into HEAD (2022-12-09 09:15:09 +0100)
>
> ...
>
>> KVM: x86: remove unnecessary exports
>
> ...
>
>> KVM: nVMX: hyper-v: Enable L2 TLB flush
>
> As reported a few times[1][2], these two collided and cause a build failure when
> building with CONFIG_KVM_AMD=m.
Ouch, the worst thing that can be reported just before a 5-day public
holiday weekend.
> ERROR: modpost: "kvm_hv_assist_page_enabled" [arch/x86/kvm/kvm-amd.ko] undefined!
> make[2]: *** [scripts/Makefile.modpost:126: Module.symvers] Error 1
> make[1]: *** [Makefile:1944: modpost] Error 2
>
> The fix is simple enough, maybe just squash it into the merge?
No, I'll fix and respin. :/
Paolo
prev parent reply other threads:[~2022-12-12 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 15:50 Paolo Bonzini
2022-12-12 16:57 ` Sean Christopherson
2022-12-12 20:41 ` Paolo Bonzini [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=6d96a62e-d5a1-e606-3bd2-c38f4a6c8545@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seanjc@google.com \
--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®