[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YUs1ejsDB4W4wKGF@zn.tnic>
Date: Wed, 22 Sep 2021 15:54:02 +0200
From: Borislav Petkov <bp@...en8.de>
To: Ashish Kalra <ashish.kalra@....com>
Cc: Sean Christopherson <seanjc@...gle.com>,
Steve Rutherford <srutherford@...gle.com>, pbonzini@...hat.com,
tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
joro@...tes.org, thomas.lendacky@....com, x86@...nel.org,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
brijesh.singh@....com, dovmurik@...ux.ibm.com, tobin@...ux.ibm.com,
jejb@...ux.ibm.com, dgilbert@...hat.com
Subject: Re: [PATCH v6 1/5] x86/kvm: Add AMD SEV specific Hypercall3
On Wed, Sep 22, 2021 at 12:10:08PM +0000, Ashish Kalra wrote:
> Then isn't it cleaner to simply do it via the paravirt_ops interface,
> i.e, pv_ops.mmu.notify_page_enc_status_changed() where the callback
> is only set when SEV and live migration feature are supported and
> invoked through early_set_memory_decrypted()/encrypted().
>
> Another memory encryption platform can set it's callback accordingly.
Yeah, that sounds even cleaner to me.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists