From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Fuad Tabba <tabba@google.com>,
Quentin Perret <qperret@google.com>,
Yuan Yao <yaoyuan@linux.alibaba.com>,
Zenghui Yu <zenghui.yu@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oupton@kernel.org>,
Zenghui Yu <yuzenghui@huawei.com>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM/arm64 fixes for 7.0, take #2
Date: Wed, 11 Mar 2026 17:04:03 +0000 [thread overview]
Message-ID: <867bri70xo.wl-maz@kernel.org> (raw)
In-Reply-To: <CABgObfYJqhj3xiM4_+7gCE1x5v5JQhyS0ox4+obrsZwA2W4GYg@mail.gmail.com>
On Wed, 11 Mar 2026 16:58:08 +0000,
Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On Fri, Mar 6, 2026 at 12:23 PM Marc Zyngier <maz@kernel.org> wrote:
> >
> > Paolo,
> >
> > Here's the second set of fixes for 7.0. The only interesting fix is
> > one affecting pKVM and preventing the host from making forward
> > progress when a memblock is not page-aligned.
> >
> > The rest is a bunch of low-severity fixes affecting the page-table
> > code, some of which Fuad has promised to start cleaning up!
> >
> > Please pull,
>
> Pulled, thanks.
As a heads up, I'm about to send another one with a couple of annoying
fixes, either today or tomorrow morning. Would be great if you could
stash that one as well.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-03-11 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 11:22 [GIT PULL] KVM/arm64 fixes for 7.0, take #2 Marc Zyngier
2026-03-11 16:58 ` Paolo Bonzini
2026-03-11 17:04 ` Marc Zyngier [this message]
2026-03-11 17:05 ` Paolo Bonzini
2026-03-11 17:41 ` Marc Zyngier
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=867bri70xo.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oupton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=qperret@google.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=yaoyuan@linux.alibaba.com \
--cc=yuzenghui@huawei.com \
--cc=zenghui.yu@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.