[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <abfb95df-4f34-1663-42e8-b9d06bab3b58@linux.intel.com>
Date: Mon, 18 Apr 2022 22:42:12 -0700
From: Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@...ux.intel.com>
To: Kai Huang <kai.huang@...el.com>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org
Cc: seanjc@...gle.com, pbonzini@...hat.com, dave.hansen@...el.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, isaku.yamahata@...el.com
Subject: Re: [PATCH v3 02/21] x86/virt/tdx: Detect TDX private KeyIDs
On 4/5/22 9:49 PM, Kai Huang wrote:
> detect_seam(c);
> + detect_tdx_keyids(c);
Do you want to add some return value to detect_seam() and not
proceed if it fails?
In case if this function is going to be extended by future
patch set, maybe do the same for detect_tdx_keyids()?
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
Powered by blists - more mailing lists