[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7d2a1ae7-56cf-a83d-4883-b2f8631a5e3d@intel.com>
Date: Tue, 13 Dec 2022 14:44:27 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Borislav Petkov <bp@...en8.de>,
Andy Lutomirski <luto@...nel.org>
Cc: Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
Elena Reshetova <elena.reshetova@...el.com>, x86@...nel.org,
linux-coco@...ts.linux.dev, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] x86/tdx: Expand __tdx_hypercall() to handle more
arguments
On 12/9/22 05:25, Kirill A. Shutemov wrote:
> So far __tdx_hypercall() only handles six arguments for VMCALL.
> Expanding it to six more register would allow to cover more use-cases.
like...
> Using RDI and RSI as VMCALL arguments requires more register shuffling.
> RAX is used to hold tdx_hypercall_args pointer and RBP stores flags.
>
> While there, fix typo in the comment on panic branch.
This isn't the world's largest patch, but it doing at least three or
four different logical things. Ideally, you'd do the restructuring in a
couple of patches and then the last one would just add the six new
registers.
Could you take 20 minutes and see if you can break this down into three
or four patches?
It looks _ok_. I'd almost ack it as-is, but it should be pretty simple
to break down.
Powered by blists - more mailing lists