[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAAq0SU=TPHQ4q8Dj583m0yfVytygN81BTEe8vU5GCOoFau+LWw@mail.gmail.com>
Date: Tue, 3 May 2022 11:38:05 -0300
From: Wander Costa <wander@...hat.com>
To: Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@...ux.intel.com>
Cc: Kai Huang <kai.huang@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
"H . Peter Anvin" <hpa@...or.com>,
"Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>,
Tony Luck <tony.luck@...el.com>,
Andi Kleen <ak@...ux.intel.com>,
Isaku Yamahata <isaku.yamahata@...il.com>,
marcelo.cerri@...onical.com, tim.gardner@...onical.com,
khalid.elmously@...onical.com, philip.cox@...onical.com,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 1/3] x86/tdx: Add TDX Guest attestation interface driver
On Mon, May 2, 2022 at 8:17 PM Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@...ux.intel.com> wrote:
> > [...]
>
> I don't want to pollute the dmesg logs if possible. For IOCTL use case,
> the return value can be used to understand the failure reason from user
> code. But for initcall failure, pr_err message is required to understand
> the failure reason.
How often is this call expected to fail?
Powered by blists - more mailing lists