[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <afe34183-4320-488f-bc03-075589bb6065@intel.com>
Date: Tue, 16 Apr 2024 09:43:06 +1200
From: "Huang, Kai" <kai.huang@...el.com>
To: Borislav Petkov <bp@...en8.de>
CC: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
<linux-kernel@...r.kernel.org>, <x86@...nel.org>, <dave.hansen@...el.com>,
<tglx@...utronix.de>, <mingo@...hat.com>, <hpa@...or.com>, <luto@...nel.org>,
<peterz@...radead.org>, <rick.p.edgecombe@...el.com>,
<thomas.lendacky@....com>, <ashish.kalra@....com>, <chao.gao@...el.com>,
<bhe@...hat.com>, <nik.borisov@...e.com>, <pbonzini@...hat.com>,
<seanjc@...gle.com>
Subject: Re: [PATCH v3 1/5] x86/kexec: do unconditional WBINVD for bare-metal
in stop_this_cpu()
On 16/04/2024 5:59 am, Borislav Petkov wrote:
> On Thu, Apr 11, 2024 at 09:54:13AM +1200, Huang, Kai wrote:
>> Could you be more specific?
>>
>> I was following Boris's suggestion to summerize all the discussion around
>> the "unconditional WBINVD" issue.
>>
>> https://lore.kernel.org/linux-kernel/20240228110207.GCZd8Sr8mXHA2KTiLz@fat_crate.local/
>>
>> I can try to improve if I can know specifically what should be trimmed down.
>
> No, keep it this way. I've yet to see someone complaining from too
> verbose commit message while doing git archeology.
>
> If it is too verbose to a reader, then that reader can jump over the
> paragraphs.
>
Yeah as replied to Kirill I am keeping it. Thanks for the feedback.
Powered by blists - more mailing lists