From: Yi Sun <yi.sun@intel.com>
To: Nikolay Borisov <nik.borisov@suse.com>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <bp@alien8.de>,
<dave.hansen@linux.intel.com>, <peterz@infradead.org>,
<x86@kernel.org>, <kirill.shutemov@linux.intel.com>,
<sathyanarayanan.kuppuswamy@linux.intel.com>,
<kai.huang@intel.com>, <linux-kernel@vger.kernel.org>,
<heng.su@intel.com>, <yi.sun@linux.intel.com>,
Dongcheng Yan <dongcheng.yan@intel.com>
Subject: Re: [PATCH v4] x86/tdx: Dump TDX version During the TD Bootup
Date: Fri, 6 Oct 2023 18:20:18 +0800 [thread overview]
Message-ID: <ZR/fN5SDW5pFX1yR@ysun46-mobl.ccr.corp.intel.com> (raw)
In-Reply-To: <2b222a2a-f749-46e8-8489-b590dc2061cb@suse.com>
On 06.10.2023 11:11, Nikolay Borisov wrote:
>
>
>On 6.10.23 г. 9:28 ч., Yi Sun wrote:
>>+static void tdg_get_sysinfo(struct tdg_sys_info *td_sys)
>>+{
>>+ u64 ret;
>>+ struct tdx_module_args args = {
>>+ .rdx = TDX_SYS_VENDOR_ID_FID,
>>+ };
>>+
>>+ if (!td_sys)
>>+ return;
>>+
>>+ memset(td_sys, 0, sizeof(struct tdg_sys_info));
>
>So in case of an error this function would effectively zero out
>tdg_sys_info and not explicitly mention that something went wrong.
>Dunno how sensible or likely it is to get an error while requesting
>the ID_FID ? Also why don't you check for errors on subsequent calls
>to TDG.SYS.RD ?
>
I'll add some error info before each error return to know what going
on when some error occurs.
Actually, I removed the error check for subsequent calls to TDG.SYS.RD
in this version, since it's probably not necessary when the first call
is successful. I can add them back with warning dumping when errors occurs.
Thanks
--Sun, Yi
next prev parent reply other threads:[~2023-10-06 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 6:28 Yi Sun
2023-10-06 8:11 ` Nikolay Borisov
2023-10-06 10:20 ` Yi Sun [this message]
2023-10-06 9:48 ` Huang, Kai
2023-10-06 11:09 ` Sun, Yi
2023-10-06 20:40 ` Huang, Kai
2023-10-09 1:23 ` Kuppuswamy Sathyanarayanan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZR/fN5SDW5pFX1yR@ysun46-mobl.ccr.corp.intel.com \
--to=yi.sun@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dongcheng.yan@intel.com \
--cc=heng.su@intel.com \
--cc=kai.huang@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nik.borisov@suse.com \
--cc=peterz@infradead.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yi.sun@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®