[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YhTlxtS6Pb4MyFwm@zn.tnic>
Date: Tue, 22 Feb 2022 14:31:50 +0100
From: Borislav Petkov <bp@...en8.de>
To: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
Cc: "Kirill A. Shutemov" <kirill@...temov.name>, aarcange@...hat.com,
ak@...ux.intel.com, dan.j.williams@...el.com,
dave.hansen@...el.com, david@...hat.com, hpa@...or.com,
jgross@...e.com, jmattson@...gle.com, joro@...tes.org,
jpoimboe@...hat.com, knsathya@...nel.org,
linux-kernel@...r.kernel.org, luto@...nel.org, mingo@...hat.com,
pbonzini@...hat.com, peterz@...radead.org,
sathyanarayanan.kuppuswamy@...ux.intel.com, sdeep@...are.com,
seanjc@...gle.com, tglx@...utronix.de, tony.luck@...el.com,
vkuznets@...hat.com, wanpengli@...cent.com, x86@...nel.org
Subject: Re: [PATCHv3.1 2.1/2] x86/coco: Add API to handle encryption mask
On Tue, Feb 22, 2022 at 02:25:38AM +0300, Kirill A. Shutemov wrote:
> I'm talking about potential issue if cc_set_vendor() and cc_set_mask()
> would drift apart.
As always, we don't code for some hypothetical case. If they do drift
apart, we'll go and fix the issue like we always do. As it turns out,
the kernel is the most flexible piece in this whole fat stack of hw and
sw so I wouldn't worry about us not being able to address any potential
"drift" apart, if it happens.
> But, okay, I see that you don't feel it an issue. Will do your way.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists