[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220221232538.3pd3w63s5v3us5xt@black.fi.intel.com>
Date: Tue, 22 Feb 2022 02:25:38 +0300
From: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
To: Borislav Petkov <bp@...en8.de>
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 Mon, Feb 21, 2022 at 11:36:55PM +0100, Borislav Petkov wrote:
> On Tue, Feb 22, 2022 at 01:10:49AM +0300, Kirill A. Shutemov wrote:
> > I'm not sure it is a good idea. It leaves room for code between these two
> > calls. I believe they conceptually has to initialized in one shot. That's
> > the only way we get consistent state.
>
> Really, where?
I'm talking about potential issue if cc_set_vendor() and cc_set_mask()
would drift apart.
But, okay, I see that you don't feel it an issue. Will do your way.
--
Kirill A. Shutemov
Powered by blists - more mailing lists