From: Paolo Bonzini <pbonzini@redhat.com>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM fixes for Linux 6.6-rc3
Date: Sun, 24 Sep 2023 17:20:31 +0200 [thread overview]
Message-ID: <c00bf4c1-0bfe-c7f9-4dea-03e9c2e94b71@redhat.com> (raw)
In-Reply-To: <5cfe9a47-f461-9a5e-09e3-b78fef16a6f6@huawei.com>
On 9/24/23 12:32, Zenghui Yu wrote:
> Hi Paolo,
>
> On 2023/9/24 17:27, Paolo Bonzini wrote:
>> ARM:
>>
>> * Fix an UV boot crash
>>
>> * Skip spurious ENDBR generation on_THIS_IP_
>>
>> * Fix ENDBR use in putuser() asm methods
>>
>> * Fix corner case boot crashes on 5-level paging
>>
>> * and fix a false positive WARNING on LTO kernels"
>
> Want to point out that this doesn't describe the *real* kvmarm stuff in
> the original PR [*] and doesn't match what you had written in the merge
> commit. Not sure what has gone wrong.
Used the wrong "git log --merges" incantation to generate the draft,
which pulled in a message from the last merge commit in origin/master.
I have replaced the tag in place, but the commit is the same. The new
tag message is as follows:
---------------------------------
ARM:
* Fix EL2 Stage-1 MMIO mappings where a random address was used
* Fix SMCCC function number comparison when the SVE hint is set
RISC-V:
* Fix KVM_GET_REG_LIST API for ISA_EXT registers
* Fix reading ISA_EXT register of a missing extension
* Fix ISA_EXT register handling in get-reg-list test
* Fix filtering of AIA registers in get-reg-list test
x86:
* Fixes for TSC_AUX virtualization
* Stop zapping page tables asynchronously, since we don't
zap them as often as before
---------------------------------
Paolo
> [*] https://lore.kernel.org/r/20230914144802.1637804-1-maz@kernel.org
>
> Zenghui
>
next prev parent reply other threads:[~2023-09-24 15:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-24 9:27 Paolo Bonzini
2023-09-24 10:32 ` Zenghui Yu
2023-09-24 15:20 ` Paolo Bonzini [this message]
2023-09-24 21:24 ` 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=c00bf4c1-0bfe-c7f9-4dea-03e9c2e94b71@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yuzenghui@huawei.com \
/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®