lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86plw71o41.wl-maz@kernel.org>
Date: Wed, 06 Mar 2024 13:33:34 +0000
From: Marc Zyngier <maz@...nel.org>
To: Ganapatrao Kulkarni <gankulkarni@...amperecomputing.com>
Cc: Oliver Upton <oliver.upton@...ux.dev>,
	kvmarm@...ts.linux.dev,
	kvm@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org,
	darren@...amperecomputing.com,
	d.scott.phillips@...erecomputing.com,
	James Morse <james.morse@....com>,
	Suzuki K Poulose <suzuki.poulose@....com>,
	Zenghui Yu <yuzenghui@...wei.com>
Subject: Re: [RFC PATCH] kvm: nv: Optimize the unmapping of shadow S2-MMU tables.

On Wed, 06 Mar 2024 05:31:09 +0000,
Ganapatrao Kulkarni <gankulkarni@...amperecomputing.com> wrote:
> 
> 
> 
> On 05-03-2024 02:16 pm, Oliver Upton wrote:
> > -cc old kvmarm list
> > +cc new kvmarm list, reviewers
> > 
> > Please run scripts/get_maintainer.pl next time around so we get the
> > right people looking at a patch.
> > 
> 
> Of course I know this script -:)
> I didn't cc since I felt to avoid unnecessary overloading someone's
> inbox. I don't think anyone(even ARM) is interested in this feature
> other than Marc and me/Ampere. Otherwise this would have merged
> upstream by now.

You're wrong on a lot of this. There is quite a significant interest,
actually. But in the fine corporate tradition, not even my employer
can be bothered to actively contribute. These people are waiting for
things to land. I'm happy to make them wait even longer (I'm paying
for my own HW, so I don't owe anyone anything).

The architecture also wasn't in a good enough state for the support to
be merged until very recently, and it still is broken in a lot of
respects.

> BTW, NV feature development started way back in 2016/17.

And? Cc'ing individuals and lists is basic courtesy, I'm afraid.
Please don't leave people in the dark.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ