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 E2F8DE743D3 for ; Fri, 29 Sep 2023 00:42:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232316AbjI2Am0 (ORCPT ); Thu, 28 Sep 2023 20:42:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36520 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232291AbjI2AmZ (ORCPT ); Thu, 28 Sep 2023 20:42:25 -0400 Received: from mail-pl1-x649.google.com (mail-pl1-x649.google.com [IPv6:2607:f8b0:4864:20::649]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5E22311F for ; Thu, 28 Sep 2023 17:42:23 -0700 (PDT) Received: by mail-pl1-x649.google.com with SMTP id d9443c01a7336-1c73fb50da6so6687545ad.0 for ; Thu, 28 Sep 2023 17:42:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1695948143; x=1696552943; darn=vger.kernel.org; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=LHnl2CsLxrfQz4bzbwJAj223y7XyxSn5JpaUfYsfSDE=; b=rC1/WGQGD7SZLSycCz9NRY4e71edtsK2IX3bbn6OuMS8KtS3xBBxX+YbzEBoQx+WWI yR1GtfF2TV8Lam5xWApyMqRy4O2Nec4K0Fyj+wWl5C3UcAaK7UtYRVvQBgInXGaHIon3 LMcwIF99+jHB/C1fChwXUfLb6EGQ3KC15/SI1hSs1X+T+tUYLVzY4DIk1JHnghsNlSts qEL+AMNKgEe0iXvO9BKE3NR/in/dEvc8r1Zeof3kNcgyTLV1Ivi6w+RrCiIGOdZ9uKhu 4TSH/YkeswaD1yWzlmgZGIghpoW58KEC2rJKv6ye9+OcLcvCVNuEHFjTan+/Y8jNUHHs PTfA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695948143; x=1696552943; 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=LHnl2CsLxrfQz4bzbwJAj223y7XyxSn5JpaUfYsfSDE=; b=DA25rv+Z6wql893xFYxhpymTMBQXg3MTuM0PYXc7oUBdJ4CNGaMCvjzbdiVNxFl3GS plxopnf+PD2w09IKyhuR96l7NksEZCfmQo3c9qegRpItvfaWLOyi61zYwC9ivXfqXW5F zPcrx5hOvOz4QElL4W4ULu4wl3qdmw6QE/xBDcEW8OCWvy3bY6V8rIk/3CUj8Y9vbu/K nYjzGmUCcsvhRY1XroPq3Yk0JAwsa5buDudsXl3yETsu/u2RwthYvzNwQAhB1xrHqbX5 cwu+CrxuWBeAjOsuY5dn3cIrm6g9lEgjse4tEfSj+1EIDv2m1Wizzp6YxRGeXXGSQLDc xPVQ== X-Gm-Message-State: AOJu0Yw0s0CyDZ0lhRUOr1h8hn3ke0+5CC6JYmwelf6Xvzt9ANAX7Oo6 mwHh3vuhkB3O6ouS35GxwUvfGYc2rak= X-Google-Smtp-Source: AGHT+IHUEPW3H4eE8hL9x01DrF8EV6/qXIdYZHJV+3Ch6SWg/Ia5upLk5S9Kq+TjsAHT50edQJbCK+giAKY= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:902:e851:b0:1c6:2b9d:570b with SMTP id t17-20020a170902e85100b001c62b9d570bmr34467plg.7.1695948142799; Thu, 28 Sep 2023 17:42:22 -0700 (PDT) Date: Thu, 28 Sep 2023 17:42:20 -0700 In-Reply-To: <20230928173354.217464-3-mlevitsk@redhat.com> Mime-Version: 1.0 References: <20230928173354.217464-1-mlevitsk@redhat.com> <20230928173354.217464-3-mlevitsk@redhat.com> Message-ID: Subject: Re: [PATCH v2 2/4] x86: KVM: SVM: add support for Invalid IPI Vector interception From: Sean Christopherson To: Maxim Levitsky Cc: kvm@vger.kernel.org, iommu@lists.linux.dev, "H. Peter Anvin" , Paolo Bonzini , Thomas Gleixner , Borislav Petkov , Joerg Roedel , x86@kernel.org, Suravee Suthikulpanit , linux-kernel@vger.kernel.org, Dave Hansen , Will Deacon , Ingo Molnar , Robin Murphy , stable@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Thu, Sep 28, 2023, Maxim Levitsky wrote: > In later revisions of AMD's APM, there is a new 'incomplete IPI' exit code: > > "Invalid IPI Vector - The vector for the specified IPI was set to an > illegal value (VEC < 16)" > > Note that tests on Zen2 machine show that this VM exit doesn't happen and > instead AVIC just does nothing. > > Add support for this exit code by doing nothing, instead of filling > the kernel log with errors. > > Also replace an unthrottled 'pr_err()' if another unknown incomplete > IPI exit happens with vcpu_unimpl() > > (e.g in case AMD adds yet another 'Invalid IPI' exit reason) > > Cc: > Signed-off-by: Maxim Levitsky > --- Reviewed-by: Sean Christopherson