Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp372212pxf; Thu, 18 Mar 2021 02:23:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxcEjtz8oWCOi9BcRA5T4aRXRxPtJLNR8gW11OlZCzZeQsRue5FlLZniY6Gw5p5NQ8U1674 X-Received: by 2002:a50:bb47:: with SMTP id y65mr2449248ede.305.1616059436763; Thu, 18 Mar 2021 02:23:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616059436; cv=none; d=google.com; s=arc-20160816; b=0lHkJmDTnEfr9D/2w1ObnoZTkEOSVgGjqNN9vehz+oQPp1Ku5AnW3IMCIk0vJHhH/u Bpz83e06/Qi998mtACTXIFtOcIuLmX8/AAXEeJxSpZUjUywGP4n2RlVkPtpfihfj0Ntr KzD5mZoyTGTRi/Sy19vHTXVWtjOJoBq42Ee3ugb+znCs79UJzkrxzeWIryEv8gDuOyU+ 22so12mveLIYQiZLOFzitXwhEoL6guEvzxd644ec+ux4SRL9x7YXgPhVEudhd8q3sxbx scubzyUBcZ8c1na7t2l30ri6KSCU6aUZfkrlLuo/1ywWlFyTSmzleQzwg6rtKdU8k4Ub +8uw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=Q1/8ZVGUvp/7zPGerNht4VLLVoVB3ievEa5z83aL2gY=; b=z+dj9DR8wT5DiZu0iMDCU9HexetJO/HxDemk5kEyIwNOi1RUSYkbIZ8CQOuwQZAZ77 MAn6vmJTRKGDW/kQVKQAFXvWYtzyFvtu32JFiy/3YSCOn3svjhxYxmZEYU+2XoNVIe0b Pq3fqp9qfnzh8NDMJh6pgkLrz0SmSxuKqf2/8EmtvfPmofVhXFjWtgD6+xJIRc0u7GgR ZsY7tHVFui7T9QsTwgYZyFZQJ4qFFEiy3BQH4gaNWRHRsdrOEIbrpNzZMryC/SaDMM8N GbOkhQ0Q20MZhlvud0Q493ufPhA1bgKgoBSNzzeEeqiXvV/MFb5WUkqw9g4+PywHijtD kXZw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=8bytes.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id gx22si1136898ejb.415.2021.03.18.02.23.34; Thu, 18 Mar 2021 02:23:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=8bytes.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229792AbhCRJUK (ORCPT + 99 others); Thu, 18 Mar 2021 05:20:10 -0400 Received: from 8bytes.org ([81.169.241.247]:59542 "EHLO theia.8bytes.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229564AbhCRJTo (ORCPT ); Thu, 18 Mar 2021 05:19:44 -0400 Received: by theia.8bytes.org (Postfix, from userid 1000) id C40F32D8; Thu, 18 Mar 2021 10:19:42 +0100 (CET) Date: Thu, 18 Mar 2021 10:19:41 +0100 From: Joerg Roedel To: Maxim Levitsky Cc: kvm@vger.kernel.org, Vitaly Kuznetsov , linux-kernel@vger.kernel.org, Thomas Gleixner , Wanpeng Li , Kieran Bingham , Jessica Yu , Jan Kiszka , Andrew Morton , "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , Sean Christopherson , Jim Mattson , Borislav Petkov , Stefano Garzarella , "H. Peter Anvin" , Paolo Bonzini , Ingo Molnar , Borislav Petkov Subject: Re: [PATCH 3/3] KVM: SVM: allow to intercept all exceptions for debug Message-ID: References: <20210315221020.661693-1-mlevitsk@redhat.com> <20210315221020.661693-4-mlevitsk@redhat.com> <4116d6ce75a85faccfe7a2b3967528f0561974ae.camel@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4116d6ce75a85faccfe7a2b3967528f0561974ae.camel@redhat.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 16, 2021 at 12:51:20PM +0200, Maxim Levitsky wrote: > I agree but what is wrong with that? > This is a debug feature, and it only can be enabled by the root, > and so someone might actually want this case to happen > (e.g to see if a SEV guest can cope with extra #VC exceptions). That doesn't make sense, we know that and SEV-ES guest can't cope with extra #VC exceptions, so there is no point in testing this. It is more a way to shot oneself into the foot for the user and a potential source of bug reports for SEV-ES guests. > I have nothing against not allowing this for SEV-ES guests though. > What do you think? I think SEV-ES guests should only have the intercept bits set which guests acutally support. Regards, Joerg