[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <36453f2f-3a2f-ae8b-215f-da9972f14d6d@amd.com>
Date: Thu, 18 Apr 2024 13:38:49 -0500
From: Tom Lendacky <thomas.lendacky@....com>
To: Borislav Petkov <bp@...en8.de>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org, linux-coco@...ts.linux.dev,
svsm-devel@...onut-svsm.dev, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Dave Hansen <dave.hansen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...or.com>, Andy Lutomirski <luto@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Dan Williams <dan.j.williams@...el.com>, Michael Roth
<michael.roth@....com>, Ashish Kalra <ashish.kalra@....com>
Subject: Re: [PATCH v3 02/14] x86/sev: Make the VMPL0 checking function more
generic
On 4/17/24 15:50, Borislav Petkov wrote:
> On Wed, Apr 17, 2024 at 03:35:53PM -0500, Tom Lendacky wrote:
>
> Yap.
>
> The point is, it is calling RMPADJUST. And it does modify RMP
> permissions of a guest page.
>
> Thus, if you prefer, you can go all out and call the helper
>
> rmp_adjust_permissions(unsigned int tgt_vmpl, void *pa)
>
> and make it generic from the get-go.
I think I'll just eliminate the function then and call rmpadjust directly,
that should make it clear.
Thanks,
Tom
>
> And then have the macro wrap around it in order to explain that
> particular use with the macro name.
>
> If it is still not clear what I mean, lemme know and I'll do a diff
> ontop.
>
> Thx.
>
Powered by blists - more mailing lists