[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <31e7d93d-0e0f-4976-bff6-84f484a8a6f3@amazon.com>
Date: Fri, 16 Jan 2026 17:32:35 +0000
From: Nikita Kalyazin <kalyazin@...zon.com>
To: Sean Christopherson <seanjc@...gle.com>, Rick P Edgecombe
<rick.p.edgecombe@...el.com>
CC: "kalyazin@...zon.co.uk" <kalyazin@...zon.co.uk>,
"linux-riscv@...ts.infradead.org" <linux-riscv@...ts.infradead.org>,
"linux-s390@...r.kernel.org" <linux-s390@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>, "linux-fsdevel@...r.kernel.org"
<linux-fsdevel@...r.kernel.org>, "linux-kselftest@...r.kernel.org"
<linux-kselftest@...r.kernel.org>, "kernel@...0n.name" <kernel@...0n.name>,
"kvmarm@...ts.linux.dev" <kvmarm@...ts.linux.dev>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"bpf@...r.kernel.org" <bpf@...r.kernel.org>, "loongarch@...ts.linux.dev"
<loongarch@...ts.linux.dev>, "linux-doc@...r.kernel.org"
<linux-doc@...r.kernel.org>, "david@...nel.org" <david@...nel.org>,
"svens@...ux.ibm.com" <svens@...ux.ibm.com>, "catalin.marinas@....com"
<catalin.marinas@....com>, "palmer@...belt.com" <palmer@...belt.com>,
"jgross@...e.com" <jgross@...e.com>, "surenb@...gle.com" <surenb@...gle.com>,
"vbabka@...e.cz" <vbabka@...e.cz>, "riel@...riel.com" <riel@...riel.com>,
"pfalcato@...e.de" <pfalcato@...e.de>, "x86@...nel.org" <x86@...nel.org>,
"rppt@...nel.org" <rppt@...nel.org>, "thuth@...hat.com" <thuth@...hat.com>,
"borntraeger@...ux.ibm.com" <borntraeger@...ux.ibm.com>, "maz@...nel.org"
<maz@...nel.org>, "peterx@...hat.com" <peterx@...hat.com>, "ast@...nel.org"
<ast@...nel.org>, Vishal Annapurve <vannapurve@...gle.com>, "pjw@...nel.org"
<pjw@...nel.org>, "alex@...ti.fr" <alex@...ti.fr>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"tglx@...utronix.de" <tglx@...utronix.de>, "hca@...ux.ibm.com"
<hca@...ux.ibm.com>, "willy@...radead.org" <willy@...radead.org>,
"wyihan@...gle.com" <wyihan@...gle.com>, "ryan.roberts@....com"
<ryan.roberts@....com>, "yang@...amperecomputing.com"
<yang@...amperecomputing.com>, "jolsa@...nel.org" <jolsa@...nel.org>,
"jmattson@...gle.com" <jmattson@...gle.com>, "luto@...nel.org"
<luto@...nel.org>, "aneesh.kumar@...nel.org" <aneesh.kumar@...nel.org>,
"haoluo@...gle.com" <haoluo@...gle.com>, "patrick.roy@...ux.dev"
<patrick.roy@...ux.dev>, "akpm@...ux-foundation.org"
<akpm@...ux-foundation.org>, "coxu@...hat.com" <coxu@...hat.com>,
"mhocko@...e.com" <mhocko@...e.com>, "mlevitsk@...hat.com"
<mlevitsk@...hat.com>, "jgg@...pe.ca" <jgg@...pe.ca>, "hpa@...or.com"
<hpa@...or.com>, "song@...nel.org" <song@...nel.org>,
"Liam.Howlett@...cle.com" <Liam.Howlett@...cle.com>, "maobibo@...ngson.cn"
<maobibo@...ngson.cn>, "peterz@...radead.org" <peterz@...radead.org>,
"oupton@...nel.org" <oupton@...nel.org>, "lorenzo.stoakes@...cle.com"
<lorenzo.stoakes@...cle.com>, "jhubbard@...dia.com" <jhubbard@...dia.com>,
"martin.lau@...ux.dev" <martin.lau@...ux.dev>, "jthoughton@...gle.com"
<jthoughton@...gle.com>, "Jonathan.Cameron@...wei.com"
<Jonathan.Cameron@...wei.com>, "Yu, Yu-cheng" <yu-cheng.yu@...el.com>,
"eddyz87@...il.com" <eddyz87@...il.com>, "yonghong.song@...ux.dev"
<yonghong.song@...ux.dev>, "chenhuacai@...nel.org" <chenhuacai@...nel.org>,
"shuah@...nel.org" <shuah@...nel.org>, "prsampat@....com" <prsampat@....com>,
"kevin.brodsky@....com" <kevin.brodsky@....com>,
"shijie@...amperecomputing.com" <shijie@...amperecomputing.com>,
"itazur@...zon.co.uk" <itazur@...zon.co.uk>, "suzuki.poulose@....com"
<suzuki.poulose@....com>, "pbonzini@...hat.com" <pbonzini@...hat.com>,
"dev.jain@....com" <dev.jain@....com>, "yuzenghui@...wei.com"
<yuzenghui@...wei.com>, "gor@...ux.ibm.com" <gor@...ux.ibm.com>,
"jackabt@...zon.co.uk" <jackabt@...zon.co.uk>, "daniel@...earbox.net"
<daniel@...earbox.net>, "agordeev@...ux.ibm.com" <agordeev@...ux.ibm.com>,
"andrii@...nel.org" <andrii@...nel.org>, "mingo@...hat.com"
<mingo@...hat.com>, "aou@...s.berkeley.edu" <aou@...s.berkeley.edu>,
"joey.gouly@....com" <joey.gouly@....com>, "derekmn@...zon.com"
<derekmn@...zon.com>, "xmarcalx@...zon.co.uk" <xmarcalx@...zon.co.uk>,
"kpsingh@...nel.org" <kpsingh@...nel.org>, "sdf@...ichev.me"
<sdf@...ichev.me>, "jackmanb@...gle.com" <jackmanb@...gle.com>,
"bp@...en8.de" <bp@...en8.de>, "corbet@....net" <corbet@....net>,
"ackerleytng@...gle.com" <ackerleytng@...gle.com>, "jannh@...gle.com"
<jannh@...gle.com>, "john.fastabend@...il.com" <john.fastabend@...il.com>,
"kas@...nel.org" <kas@...nel.org>, "will@...nel.org" <will@...nel.org>
Subject: Re: [PATCH v9 07/13] KVM: guest_memfd: Add flag to remove from direct
map
On 16/01/2026 15:41, Sean Christopherson wrote:
> On Fri, Jan 16, 2026, Rick P Edgecombe wrote:
>> On Fri, 2026-01-16 at 15:02 +0000, Nikita Kalyazin wrote:
>>>> TDX does some clearing at the direct map mapping for pages that
>>>> comes from gmem, using a special instruction. It also does some
>>>> clflushing at the direct map address for these pages. So I think we
>>>> need to make sure TDs don't pull from gmem fds with this flag.
>>>
>>> Would you be able to give a pointer on how we can do that? I'm not
>>> very familiar with the TDX code.
>>
>> Uhh, that is a good question. Let me think.
>
> Pass @kvm to kvm_arch_gmem_supports_no_direct_map() and then return %false if
> it's a TDX VM.
Sounds good to me, thanks.
Powered by blists - more mailing lists