From: Paolo Bonzini <pbonzini@redhat.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Denis Nikitin <denik@chromium.org>,
Eric Auger <eric.auger@redhat.com>,
Eric Ren <renzhengeek@gmail.com>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Alexandru Elisei <alexandru.elisei@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
kvmarm@lists.cs.columbia.edu, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM/arm64 fixes for 6.1, take #2
Date: Sat, 22 Oct 2022 09:33:40 +0200 [thread overview]
Message-ID: <CABgObfYexXFT507Ufz3o2SLOAVDWO1AhJV5yKi9Ar1OeLNnPSQ@mail.gmail.com> (raw)
In-Reply-To: <20221020100125.3670769-1-maz@kernel.org>
On Thu, Oct 20, 2022 at 12:02 PM Marc Zyngier <maz@kernel.org> wrote:
>
> Paolo,
>
> Here's a couple of additional fixes for 6.1. The ITS one is pretty
> annoying as it prevents a VM from being restored if it has a
> convoluted device topology. Definitely a stable candidate.
>
> Note that I can't see that you have pulled the first set of fixes
> which I sent last week[1]. In order to avoid any problem, the current
> pull-request is a suffix of the previous one. But you may want to pull
> them individually in order to preserve the tag descriptions.
Yes, that's why I did. Pulled now, thanks.
Paolo
>
> Please pull,
>
> M.
>
> [1] https://lore.kernel.org/r/20221013132830.1304947-1-maz@kernel.org
>
> The following changes since commit 05c2224d4b049406b0545a10be05280ff4b8ba0a:
>
> KVM: selftests: Fix number of pages for memory slot in memslot_modification_stress_test (2022-10-13 11:46:51 +0100)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-6.1-2
>
> for you to fetch changes up to c000a2607145d28b06c697f968491372ea56c23a:
>
> KVM: arm64: vgic: Fix exit condition in scan_its_table() (2022-10-15 12:10:54 +0100)
>
> ----------------------------------------------------------------
> KVM/arm64 fixes for 6.1, take #2
>
> - Fix a bug preventing restoring an ITS containing mappings
> for very large and very sparse device topology
>
> - Work around a relocation handling error when compiling
> the nVHE object with profile optimisation
>
> ----------------------------------------------------------------
> Denis Nikitin (1):
> KVM: arm64: nvhe: Fix build with profile optimization
>
> Eric Ren (1):
> KVM: arm64: vgic: Fix exit condition in scan_its_table()
>
> arch/arm64/kvm/hyp/nvhe/Makefile | 4 ++++
> arch/arm64/kvm/vgic/vgic-its.c | 5 ++++-
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-10-22 7:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 10:01 [GIT PULL] KVM/arm64 fixes for 6.1, take #2 Marc Zyngier
2022-10-22 7:33 ` 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=CABgObfYexXFT507Ufz3o2SLOAVDWO1AhJV5yKi9Ar1OeLNnPSQ@mail.gmail.com \
--to=pbonzini@redhat.com \
--cc=alexandru.elisei@arm.com \
--cc=denik@chromium.org \
--cc=eric.auger@redhat.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=renzhengeek@gmail.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).