From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9E16CC4332F for ; Wed, 22 Sep 2021 13:54:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 886636120E for ; Wed, 22 Sep 2021 13:54:16 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233926AbhIVNzo (ORCPT ); Wed, 22 Sep 2021 09:55:44 -0400 Received: from mail.skyhub.de ([5.9.137.197]:41376 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233479AbhIVNzo (ORCPT ); Wed, 22 Sep 2021 09:55:44 -0400 Received: from zn.tnic (p200300ec2f0efa00329c23fffea6a903.dip0.t-ipconnect.de [IPv6:2003:ec:2f0e:fa00:329c:23ff:fea6:a903]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id 6F8851EC0537; Wed, 22 Sep 2021 15:54:08 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1632318848; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:in-reply-to:in-reply-to: references:references; bh=AiNJ05ptDQZvBWlLVMY8+uuVH6308VUGaXejpuvkXds=; b=G3aT8PSdyMqfAojp8ManX9HaECqAU15N6iJXV2Vg/CpSgwC7gfx4j5B8F5eR5jeJ/NRoJg PQTJj7yRJ2GDrAjjQfW9Sf40asscQ+YiYYq8tK8SQCkVnwft0UC34hVVPYZOuoMC2dpMWW Z7AZPT6WKxZVXa+/4Nesnrc1Gy/Nzdg= Date: Wed, 22 Sep 2021 15:54:02 +0200 From: Borislav Petkov To: Ashish Kalra Cc: Sean Christopherson , Steve Rutherford , pbonzini@redhat.com, tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, joro@8bytes.org, thomas.lendacky@amd.com, x86@kernel.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, brijesh.singh@amd.com, dovmurik@linux.ibm.com, tobin@linux.ibm.com, jejb@linux.ibm.com, dgilbert@redhat.com Subject: Re: [PATCH v6 1/5] x86/kvm: Add AMD SEV specific Hypercall3 Message-ID: References: <6fd25c749205dd0b1eb492c60d41b124760cc6ae.1629726117.git.ashish.kalra@amd.com> <20210921095838.GA17357@ashkalra_ubuntu_server> <20210922121008.GA18744@ashkalra_ubuntu_server> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210922121008.GA18744@ashkalra_ubuntu_server> Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org 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