From: Catalin Marinas <catalin.marinas@arm.com>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: Marc Zyngier <maz@kernel.org>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Will Deacon <will@kernel.org>, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH] arm64: Expose ID_AA64ISAR1_EL1.XS to sanitised feature consumers
Date: Fri, 1 Nov 2024 16:35:00 +0000 [thread overview]
Message-ID: <ZyUDNCu-vYh_tpKv@arm.com> (raw)
In-Reply-To: <ZyT4JG1Nec_xPCHH@linux.dev>
On Fri, Nov 01, 2024 at 08:47:48AM -0700, Oliver Upton wrote:
> On Fri, Nov 01, 2024 at 03:35:41PM +0000, Catalin Marinas wrote:
> > On Thu, Oct 31, 2024 at 08:35:19AM +0000, Marc Zyngier wrote:
> > > Despite KVM now being able to deal with XS-tagged TLBIs, we still don't
> > > expose these feature bits to KVM.
> > >
> > > Plumb in the feature in ID_AA64ISAR1_EL1.
> > >
> > > Fixes: 0feec7769a63 ("KVM: arm64: nv: Add handling of NXS-flavoured TLBI operations")
> > > Signed-off-by: Marc Zyngier <maz@kernel.org>
> >
> > Acked-by: Catalin Marinas <catalin.marinas@arm.com>
> >
> > Happy for this to go in as a fix via the kvm tree but let me know if I
> > should pick it up instead.
>
> Thanks Catalin. I think this can wait for 6.13, would you mind grabbing
> it?
>
> If you do:
>
> Reviewed-by: Oliver Upton <oliver.upton@linux.dev>
I'll pick it up. Thanks.
--
Catalin
next prev parent reply other threads:[~2024-11-01 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 8:35 [PATCH] arm64: Expose ID_AA64ISAR1_EL1.XS to sanitised feature consumers Marc Zyngier
2024-11-01 15:35 ` Catalin Marinas
2024-11-01 15:47 ` Oliver Upton
2024-11-01 16:35 ` Catalin Marinas [this message]
2024-11-01 16:12 ` Marc Zyngier
2024-11-01 17:36 ` Catalin Marinas
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=ZyUDNCu-vYh_tpKv@arm.com \
--to=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).