[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b9a17b7f6e85ffb4bc9f318bdfe0a952b5ae2445.camel@intel.com>
Date: Wed, 25 Jun 2025 21:46:41 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "seanjc@...gle.com" <seanjc@...gle.com>
CC: "Gao, Chao" <chao.gao@...el.com>, "Hansen, Dave" <dave.hansen@...el.com>,
"x86@...nel.org" <x86@...nel.org>, "Huang, Kai" <kai.huang@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"mingo@...hat.com" <mingo@...hat.com>, "kirill.shutemov@...ux.intel.com"
<kirill.shutemov@...ux.intel.com>, "bp@...en8.de" <bp@...en8.de>,
"pbonzini@...hat.com" <pbonzini@...hat.com>, "Zhao, Yan Y"
<yan.y.zhao@...el.com>, "linux-coco@...ts.linux.dev"
<linux-coco@...ts.linux.dev>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>, "Yamahata, Isaku"
<isaku.yamahata@...el.com>
Subject: Re: [PATCHv2 01/12] x86/tdx: Consolidate TDX error handling
On Wed, 2025-06-25 at 14:27 -0700, Sean Christopherson wrote:
> Can we turn them into macros that make it super obvious they are checking if the
> error code *is* xyz? E.g.
>
> #define IS_TDX_ERR_OPERAND_BUSY
> #define IS_TDX_ERR_OPERAND_INVALID
> #define IS_TDX_ERR_NO_ENTROPY
> #define IS_TDX_ERR_SW_ERROR
Good idea.
Powered by blists - more mailing lists