From: Marc Zyngier <maz@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Vincent Donnefort <vdonnefort@google.com>,
Will Deacon <will@kernel.org>, James Morse <james.morse@arm.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
Mark Rutland <mark.rutland@arm.com>,
Oliver Upton <oupton@kernel.org>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
Sudeep Holla <sudeep.holla@kernel.org>
Subject: Re: [PATCH v2] KVM: arm64: Work around C1-Pro erratum 4193714 for protected guests
Date: Wed, 06 May 2026 17:06:56 +0100 [thread overview]
Message-ID: <86y0hwy127.wl-maz@kernel.org> (raw)
In-Reply-To: <afti13dXA6DjGXR3@arm.com>
On Wed, 06 May 2026 16:48:39 +0100,
Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> On Wed, May 06, 2026 at 02:37:41PM +0100, Vincent Donnefort wrote:
> > On Tue, May 05, 2026 at 05:52:03PM +0100, Catalin Marinas wrote:
> > > diff --git a/arch/arm64/kvm/hyp/nvhe/mem_protect.c b/arch/arm64/kvm/hyp/nvhe/mem_protect.c
> > > index 28a471d1927c..7d59faa99fee 100644
> > > --- a/arch/arm64/kvm/hyp/nvhe/mem_protect.c
> > > +++ b/arch/arm64/kvm/hyp/nvhe/mem_protect.c
> > > @@ -5,6 +5,8 @@
> > > */
> > >
> > > #include <linux/kvm_host.h>
> > > +#include <linux/arm-smccc.h>
> > > +
> >
> > nit: probably not necessary with the nvhe/arm-smccc.h include below.
>
> Ah, yes. Some left-over from before I changed it to use hyp_smccc_* and
> had to include nvhe/arm-smccc.h.
>
> Marc, do you want me to respin or you can drop this include when
> applying.
I'll fix it locally, no need to resend.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-05-06 16:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 16:52 [PATCH v2] KVM: arm64: Work around C1-Pro erratum 4193714 for protected guests Catalin Marinas
2026-05-06 13:37 ` Vincent Donnefort
2026-05-06 14:21 ` Marc Zyngier
2026-05-06 15:48 ` Catalin Marinas
2026-05-06 16:06 ` Marc Zyngier [this message]
2026-05-06 16:14 ` 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=86y0hwy127.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=oupton@kernel.org \
--cc=sudeep.holla@kernel.org \
--cc=vdonnefort@google.com \
--cc=will@kernel.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