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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4AD45C77B7A for ; Tue, 6 Jun 2023 18:49:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239106AbjFFStF (ORCPT ); Tue, 6 Jun 2023 14:49:05 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58208 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239128AbjFFSsu (ORCPT ); Tue, 6 Jun 2023 14:48:50 -0400 Received: from mail-pj1-x1049.google.com (mail-pj1-x1049.google.com [IPv6:2607:f8b0:4864:20::1049]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9B4E4173C for ; Tue, 6 Jun 2023 11:48:48 -0700 (PDT) Received: by mail-pj1-x1049.google.com with SMTP id 98e67ed59e1d1-256419413a3so4484998a91.0 for ; Tue, 06 Jun 2023 11:48:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1686077328; x=1688669328; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=fN0Fls1U74QCQM1Xm6ZYG4bCrufqtPp5nAnLDL+EUzE=; b=FwQXYRBxBJBGXt1Lq7luAzvVT4DDyzoXVPP8VB7AHg2yHiHbpo6AmHR3BLCubiDzY1 m+7p40bUs9ndbSQxs9i2hNhFTSYzhA2Ad8c0Zb4QgBSYdfSAds/+4xzyCHpWUZHJ9yvu AZGILlP244CpP86XBey+8iLx7C9zzx2103w5IXOwtM1ug40RI1AQBVJNdMqBFD+St9TV rZ8GLA4QlMpSRV9ZdSNJVU0neFkTc8ykG6gmIMuXawiD9vkTU7PR1C/uDnt26o8Q6xsB bu6f4yXDFNB/9Hzumk2tEshQ/7DFLH6p6bA6h+ZOB7v1xyuVN3UP3W7410NqcfGLrNF1 Ou0w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686077328; x=1688669328; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=fN0Fls1U74QCQM1Xm6ZYG4bCrufqtPp5nAnLDL+EUzE=; b=MzSHgC56xuYK+q2SLFa6Y9DCz6WJEzd5ATq1Bo3QShjL6mXJAQb8p7GrQHiv00SM+0 Bj9NOE5OVjAN2MEaaBYR1BX4+pxOzj35k14v7kj8FNRa6c6qf1CtNghgxocFjWvk8u6p qX7tYqaTuwuqltGMxWk3rG9CzJlOI8Fe82f2opH67B06hbNiKtabfuCDCoq8Hj6nYxrW s5LVduimFg8r4hksl38xsRtEMZv2t9GsHS8g5Q/Vd97VyzROT4iIyQJCYcEKWIvUvgo5 sDuVs5V1lpJyxRUWkyGaFkVeksv6ODSSUROzOKwRDrRTexsixEYtzenuZ+yxMPkYnJHE KUZQ== X-Gm-Message-State: AC+VfDyDRMJVvz0AGwxIifBtJQVcSb3cdmnidrRWfxZyP/M6e3QeTL7+ TdDsqJDKK3WaymSn9AwGpiftSsk9FUA= X-Google-Smtp-Source: ACHHUZ4cZk+uYmAHt8bLFAANuelXzq0fKbAwTD4UgjWe2H34B4Bp0ysoDuMLU8JEKzLDj67jxa/gQ8Vy5NA= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:90a:cb97:b0:259:ae68:858d with SMTP id a23-20020a17090acb9700b00259ae68858dmr388903pju.1.1686077327954; Tue, 06 Jun 2023 11:48:47 -0700 (PDT) Date: Tue, 6 Jun 2023 11:48:40 -0700 In-Reply-To: <20230522161249.800829-1-aleksandr.mikhalitsyn@canonical.com> Mime-Version: 1.0 References: <20230522161249.800829-1-aleksandr.mikhalitsyn@canonical.com> X-Mailer: git-send-email 2.41.0.162.gfafddb0af9-goog Message-ID: <168607721796.1301198.548168594619269524.b4-ty@google.com> Subject: Re: [PATCH v2 0/2] KVM: SVM: small tweaks for sev_hardware_setup From: Sean Christopherson To: Sean Christopherson , pbonzini@redhat.com, Alexander Mikhalitsyn Cc: "=?UTF-8?q?St=C3=A9phane=20Graber?=" , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" Content-Type: text/plain; charset="utf-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 22 May 2023 18:12:46 +0200, Alexander Mikhalitsyn wrote: > KVM: SVM: enhance info printk's in SEV init > > Let's print available ASID ranges for SEV/SEV-ES guests. > This information can be useful for system administrator > to debug if SEV/SEV-ES fails to enable. > > There are a few reasons. > SEV: > - NPT is disabled (module parameter) > - CPU lacks some features (sev, decodeassists) > - Maximum SEV ASID is 0 > > [...] Applied [2/2] to kvm-x86 svm, with the minor fixup. I'll post a formal patch for the alternative approach to "fixing" the leak, I can always circle back to this series if this approach is preferred. Thanks! [2/2] KVM: SVM: enhance info printk's in SEV init https://github.com/kvm-x86/linux/commit/6d1bc9754b04 -- https://github.com/kvm-x86/linux/tree/next https://github.com/kvm-x86/linux/tree/fixes