[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <y6k6j3kzoaze3gk4duhxhca6vq6mll2n3iabrm32o4mi3qi2hz@4nanpujhbkib>
Date: Thu, 24 Apr 2025 13:39:16 +0300
From: "Kirill A. Shutemov" <kirill@...temov.name>
To: Yan Zhao <yan.y.zhao@...el.com>
Cc: pbonzini@...hat.com, seanjc@...gle.com, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, x86@...nel.org, rick.p.edgecombe@...el.com,
dave.hansen@...el.com, kirill.shutemov@...el.com, tabba@...gle.com,
ackerleytng@...gle.com, quic_eberman@...cinc.com, michael.roth@....com, david@...hat.com,
vannapurve@...gle.com, vbabka@...e.cz, jroedel@...e.de, thomas.lendacky@....com,
pgonda@...gle.com, zhiquan1.li@...el.com, fan.du@...el.com, jun.miao@...el.com,
ira.weiny@...el.com, chao.p.peng@...el.com
Subject: Re: [RFC PATCH 00/21] KVM: TDX huge page support for private memory
On Thu, Apr 24, 2025 at 05:49:17PM +0800, Yan Zhao wrote:
> > Accepting everything at 4k level is a stupid, but valid behaviour on the
> > guest behalf. This splitting case has to be supported before the patchset
> > hits the mainline.
> Hmm. If you think this is a valid behavior, patches to introduce more locks
> in TDX are required :)
>
> Not sure about the value of supporting it though, as it's also purely
> hypothetical and couldn't exist in Linux guests.
Linux is not the only possible guest.
--
Kiryl Shutsemau / Kirill A. Shutemov
Powered by blists - more mailing lists