[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230727171008.aw3z6oxh4vfnahep@box.shutemov.name>
Date: Thu, 27 Jul 2023 20:10:08 +0300
From: kirill.shutemov@...ux.intel.com
To: Kai Huang <kai.huang@...el.com>
Cc: peterz@...radead.org, linux-kernel@...r.kernel.org,
dave.hansen@...el.com, tglx@...utronix.de, bp@...en8.de,
mingo@...hat.com, hpa@...or.com, x86@...nel.org, seanjc@...gle.com,
pbonzini@...hat.com, isaku.yamahata@...el.com,
sathyanarayanan.kuppuswamy@...ux.intel.com,
n.borisov.lkml@...il.com
Subject: Re: [PATCH v3 07/12] x86/tdx: Make TDX_HYPERCALL asm similar to
TDX_MODULE_CALL
On Wed, Jul 26, 2023 at 11:25:09PM +1200, Kai Huang wrote:
>
> Remove the __tdx_hypercall_ret() as __tdx_hypercall() already does so.
Hm. So we now update struct on all VMCALLs. Is it a good idea? We give
more control to VMM where it is not needed. I would rather keep the struct
read-only where possible.
--
Kiryl Shutsemau / Kirill A. Shutemov
Powered by blists - more mailing lists