[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3253e9fa-14f8-085e-5f13-bb70fea89abf@intel.com>
Date: Mon, 27 Jun 2022 15:57:07 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Kai Huang <kai.huang@...el.com>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org
Cc: seanjc@...gle.com, pbonzini@...hat.com, len.brown@...el.com,
tony.luck@...el.com, rafael.j.wysocki@...el.com,
reinette.chatre@...el.com, dan.j.williams@...el.com,
peterz@...radead.org, ak@...ux.intel.com,
kirill.shutemov@...ux.intel.com,
sathyanarayanan.kuppuswamy@...ux.intel.com,
isaku.yamahata@...el.com
Subject: Re: [PATCH v5 15/22] x86/virt/tdx: Allocate and set up PAMTs for
TDMRs
On 6/27/22 15:50, Kai Huang wrote:
>> Are Kirill's magic 0/1/2 numbers the same as
>>
>> TDX_PG_4K,
>> TDX_PG_2M,
>> TDX_PG_1G,
>>
>> ?
> Yes they are the same. Kirill uses 0/1/2 as input of TDX_ACCEPT_PAGE TDCALL.
> Here I only need them to distinguish different page sizes.
>
> Do you mean we should put TDX_PG_4K/2M/1G definition to asm/tdx.h, and
> try_accept_one() should use them instead of magic 0/1/2?
I honestly don't care how you do it as long as the magic numbers go away
(within reason).
Powered by blists - more mailing lists