Received-SPF: pass (google.com: domain of linux-kernel+bounces-128346-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Tue, 2 Apr 2024 17:20:36 +0100
From: Mark Brown <broonie@kernel.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Oliver Upton <oliver.upton@linux.dev>,
	James Morse <james.morse@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Jonathan Corbet <corbet@lwn.net>, Shuah Khan <shuah@kernel.org>,
	linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org,
	Dave Martin <Dave.Martin@arm.com>, kvmarm@lists.linux.dev,
	linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v6 1/5] KVM: arm64: Share all userspace hardened thread
 data with the hypervisor
Message-ID: <562e1ddb-75e5-4c02-83ea-b946b88d35c8@sirena.org.uk>
References: <20240329-arm64-2023-dpisa-v6-0-ba42db6c27f3@kernel.org>
 <20240329-arm64-2023-dpisa-v6-1-ba42db6c27f3@kernel.org>
 <87msqesoty.wl-maz@kernel.org>
 <fb54d7b0-9c83-4a0c-a08b-b722c9381ca7@sirena.org.uk>
 <86h6gju87m.wl-maz@kernel.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="ZsRoYufVRq8HDIbM"
Content-Disposition: inline
In-Reply-To: <86h6gju87m.wl-maz@kernel.org>


--ZsRoYufVRq8HDIbM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Apr 02, 2024 at 03:53:33PM +0100, Marc Zyngier wrote:
> Mark Brown <broonie@kernel.org> wrote:

> > Sure, those patches are still in flight though.  It does seem reasonable
> > to target the current code.

> Sure, if your intent is for this code not to be merged.

> Because it means this series assumes a different data life cycle, and
> the review effort spent on it will be invalidated once you move to the
> per-CPU state.

I don't have any visibility on when those patches are likely to get
merged or the general practices with in flight serieses here, last time
around with some of the serieses that were in flight it was quite late
which did make it unclear if things would go in during that release
cycle at all.

The amount of churn in KVM recently and long periods where the relevant
patches are apparently pre accepted but for various not always clear
reasons not actually merged is making it quite hard to target, you're
obviously going to be a lot more in the loop so this is doubtless
clearer to you than to me.  It's also been a little unclear what the
expectations are for basing things on - some people do prefer to do
their own merging for example, and while you have mentioned your in
flight serieses your communication style means that it's not been
entirely clear if you're just noting the overlap.  Is it just that
refactoring series you want taking into account here or are there other
in flight serieses that should be rolled into a base?

--ZsRoYufVRq8HDIbM
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmYMMFQACgkQJNaLcl1U
h9BDVQf/cg+fzd23KIrGiAWOOdVY4LvIfnSbQLI4D21tWm3gJlGZ6eImlJ62QQAU
8JaTbACh3U8/tV6s/6g6FUKVobLvFA/iU1+n4VZEQ48Ff4f3o+TWJQVAwpGq2PXJ
mkpNQmxOHLPIoE2oGDz3sSBu+6A888trmpCyidGfy8NA5+5N6JPAV8wlv57XBo/C
tN+utUoWo9Kk4wQEcuimfo1hCIKWQDY/wtDLfCsgjTdEvelyGo/fdGQwmb4fskoV
LIi/ZxVwlhrToV8IqnwYirKQLt0eeE5oy0ExSfR26SJP8d6uFzhEFzyhSPx3aCJd
LcbhFstoGtpCqu90KCaYfleTeza12g==
=lAvr
-----END PGP SIGNATURE-----

--ZsRoYufVRq8HDIbM--