From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Andrew Scull <ascull@google.com>,
David Brazdil <dbrazdil@google.com>,
James Morse <james.morse@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
kernel-team@android.com
Subject: [GIT PULL] KVM/arm64 fixes for 5.11, take #3
Date: Thu, 28 Jan 2021 17:58:30 +0000 [thread overview]
Message-ID: <20210128175830.3035035-1-maz@kernel.org> (raw)
Hi Paolo,
Hopefully this is the last KVM/arm64 fix for 5.11, addressing a
register corruption at boot time, which got unnoticed until Andrew had
a closer look at it. Thankfully, this is only in 5.11, so it was
caught in time.
Please pull,
M.
The following changes since commit 139bc8a6146d92822c866cf2fd410159c56b3648:
KVM: Forbid the use of tagged userspace addresses for memslots (2021-01-21 14:17:36 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-5.11-3
for you to fetch changes up to e500b805c39daff2670494fff94909d7e3d094d9:
KVM: arm64: Don't clobber x4 in __do_hyp_init (2021-01-25 15:50:35 +0000)
----------------------------------------------------------------
KVM/arm64 fixes for 5.11, take #3
- Avoid clobbering extra registers on initialisation
----------------------------------------------------------------
Andrew Scull (1):
KVM: arm64: Don't clobber x4 in __do_hyp_init
arch/arm64/kvm/hyp/nvhe/hyp-init.S | 20 +++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
next reply other threads:[~2021-01-28 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 17:58 Marc Zyngier [this message]
2021-01-28 18:02 ` [GIT PULL] KVM/arm64 fixes for 5.11, take #3 Paolo Bonzini
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=20210128175830.3035035-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=ascull@google.com \
--cc=dbrazdil@google.com \
--cc=james.morse@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=pbonzini@redhat.com \
--cc=suzuki.poulose@arm.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;
as well as URLs for NNTP newsgroup(s).