Received-SPF: pass (google.com: domain of linux-kernel+bounces-47399-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Reply-To: Sean Christopherson <seanjc@google.com>
Date: Wed, 31 Jan 2024 15:56:05 -0800
Precedence: bulk
Mime-Version: 1.0
Message-ID: <20240131235609.4161407-1-seanjc@google.com>
Subject: [PATCH v4 0/4] Add support for allowing zero SEV ASIDs
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, 
	Ashish Kalra <ashish.kalra@amd.com>, Tom Lendacky <thomas.lendacky@amd.com>
Content-Type: text/plain; charset="UTF-8"

Play nice with systems where SEV and SEV-ES are enabled, but all ASIDs
have been carved out for SEV-eS, i.e. where actually running SEV guests
is impossible.

v4:
 - Convert all ASID usage to unsigned integers.
 - Clean up sev_asid_new() so that it doesn't needlessly overload its
   return value.
 - Split out the -EBUSY=>-EINVAL change to a separate patch.

v3: https://lore.kernel.org/all/20240104190520.62510-1-Ashish.Kalra@amd.com

Ashish Kalra (1):
  KVM: SVM: Add support for allowing zero SEV ASIDs

Sean Christopherson (3):
  KVM: SVM: Set sev->asid in sev_asid_new() instead of overloading the
    return
  KVM: SVM: Use unsigned integers when dealing with ASIDs
  KVM: SVM: Return -EINVAL instead of -EBUSY on attempt to re-init
    SEV/SEV-ES

 arch/x86/kvm/svm/sev.c | 58 +++++++++++++++++++++++++-----------------
 arch/x86/kvm/trace.h   | 10 ++++----
 2 files changed, 39 insertions(+), 29 deletions(-)


base-commit: 41bccc98fb7931d63d03f326a746ac4d429c1dd3
-- 
2.43.0.429.g432eaa2c6b-goog