linux-kernel - Re: [RFC PATCH 26/39] KVM: guest_memfd: Track faultability within a struct kvm_gmem

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20241016115737.GC3559746@nvidia.com>
Date: Wed, 16 Oct 2024 08:57:37 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: David Hildenbrand <david@...hat.com>
Cc: Vishal Annapurve <vannapurve@...gle.com>,
	Ackerley Tng <ackerleytng@...gle.com>, Peter Xu <peterx@...hat.com>,
	tabba@...gle.com, quic_eberman@...cinc.com, roypat@...zon.co.uk,
	rientjes@...gle.com, fvdl@...gle.com, jthoughton@...gle.com,
	seanjc@...gle.com, pbonzini@...hat.com, zhiquan1.li@...el.com,
	fan.du@...el.com, jun.miao@...el.com, isaku.yamahata@...el.com,
	muchun.song@...ux.dev, erdemaktas@...gle.com, qperret@...gle.com,
	jhubbard@...dia.com, willy@...radead.org, shuah@...nel.org,
	brauner@...nel.org, bfoster@...hat.com, kent.overstreet@...ux.dev,
	pvorel@...e.cz, rppt@...nel.org, richard.weiyang@...il.com,
	anup@...infault.org, haibo1.xu@...el.com, ajones@...tanamicro.com,
	vkuznets@...hat.com, maciej.wieczor-retman@...el.com,
	pgonda@...gle.com, oliver.upton@...ux.dev,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	kvm@...r.kernel.org, linux-kselftest@...r.kernel.org
Subject: Re: [RFC PATCH 26/39] KVM: guest_memfd: Track faultability within a
 struct kvm_gmem_private

On Wed, Oct 16, 2024 at 01:54:32PM +0200, David Hildenbrand wrote:

> Likely should be doable. All we need is the generalized concept of a folio
> with HVO, and a way to move these folios between owners (e.g.,
> global<->hugetlb, global<->guest_memfd).

+1

HVO seems to become a sticking point in these discussions, having a
way to make any big folio HVO optimized (and undo it) then put hugetlb
on top of that would be a nice refactoring.

Jason