[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <d8c924b5-d4f8-4a53-af8b-e393f64d036f@intel.com>
Date: Wed, 15 May 2024 06:53:17 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Nikolay Borisov <nik.borisov@...e.com>
Cc: Dave Hansen <dave.hansen@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>, linux-coco@...ts.linux.dev,
linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCHv4 3/4] x86/tdx: Dynamically disable SEPT violations from
causing #VEs
On 5/15/24 02:30, Kirill A. Shutemov wrote:
>> nit: Perhaps this function can be put in the first patch and the description
>> there be made more generic, something along the lines of "introduce
>> functions for tdg_rd/tdg_wr" ?
> A static function without an user will generate a build warning. I don't
> think it is good idea.
OK, so stick a __maybe_unused on it when you define it and remove it on
first use.
Powered by blists - more mailing lists