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 09AE2C71133 for ; Fri, 25 Aug 2023 19:03:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229554AbjHYTDJ (ORCPT ); Fri, 25 Aug 2023 15:03:09 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40914 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231226AbjHYTC6 (ORCPT ); Fri, 25 Aug 2023 15:02:58 -0400 Received: from mail-yw1-x1149.google.com (mail-yw1-x1149.google.com [IPv6:2607:f8b0:4864:20::1149]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 359872691 for ; Fri, 25 Aug 2023 12:02:47 -0700 (PDT) Received: by mail-yw1-x1149.google.com with SMTP id 00721157ae682-58fc4291239so18557857b3.0 for ; Fri, 25 Aug 2023 12:02:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1692990166; x=1693594966; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=lkF8HC++Qf7cGjgxZMsjOTZMESDaoCpW5C43MWMv8aM=; b=LXNX5TA8aHnFLADA7zjZOU3xdGUcDEqnmFhm/ONADp0hqgd4llq9OS6VyO/VRtR8or LhIqzc7eA8V4jQn5Z9PVgQLha9+qkruVN4IAEpFPFn6SjRC2TvA6Zke2lcW0jqGScvcH 0bhY2rlGQINC5qFWDGT0hJ9dE9RQ7fG8lr/ejLh+OblV3TpdlzHYvvAp3Ghm10kncRfd 7fSWvxgsQaTF7jkNCRPE9h0rJNXZuoPKVnw2uXMZvmGA4RVHUGRHgwb0uB8hVgJTznZV KiZ75GotczosQLt+ty5serzwwItp9xxdlKCSiXb1zI+kAWhtijtdbZmeMQwJtOZelp54 2ntw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692990166; x=1693594966; 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=lkF8HC++Qf7cGjgxZMsjOTZMESDaoCpW5C43MWMv8aM=; b=KJnQaFpeJxk8OVDqmkhA31oOodeyuFBnqhXqLWq5LUeWcCShU8/0oO0VEh4zGJmKoe KkSSk9mlHDVHQ+n+fg/7Z6rXlK4VO4UHjXepCSJQ0XFGn0zRD9UueBohC0fOEuY4KbYT l+6LY6BU3Ai3OZZLKKuAzpTdZV+6W6mKkWMWBRfOmXsUcQbKaqTba/Mv02YXTIaCBlOr SVHcUYd6p6Df2gkSvJux6edNt/cMCrQ5ieWABs+x82CKrau7TcuS99JUgIkLqiBmCnD1 np3/27RxSwfzhxguSb18JS9xYjyYCHz3zciAd10pHP5C763NWjeYRFYmjHcol7dr0bx/ bncA== X-Gm-Message-State: AOJu0Ywyeb7VttNQhYl7VKZA2elCbbzOS6RYoDGNzS2YN7ofZlaVqLY9 r3ijXzT+bl8HqFYC0ylXBPDes521G7M= X-Google-Smtp-Source: AGHT+IGjyRCLQFc9+X3WZ1j6KjcKHNfotrK+SO1usxAAAAeEtt4NbM3dx4n+qBep7RoJ7YlWU/BYmqD0hxg= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a81:b660:0:b0:573:5797:4b9e with SMTP id h32-20020a81b660000000b0057357974b9emr527684ywk.1.1692990166490; Fri, 25 Aug 2023 12:02:46 -0700 (PDT) Date: Fri, 25 Aug 2023 12:02:42 -0700 In-Reply-To: <20230815174215.433222-1-seanjc@google.com> Mime-Version: 1.0 References: <20230815174215.433222-1-seanjc@google.com> X-Mailer: git-send-email 2.42.0.rc2.253.gd59a3bf2b4-goog Message-ID: <169297955779.2871906.7970773718400668561.b4-ty@google.com> Subject: Re: [PATCH] KVM: VMX: Delete ancient pr_warn() about KVM_SET_TSS_ADDR not being set From: Sean Christopherson To: Sean Christopherson , Paolo Bonzini Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Thorsten Glaser Content-Type: text/plain; charset="utf-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 15 Aug 2023 10:42:15 -0700, Sean Christopherson wrote: > Delete KVM's printk about KVM_SET_TSS_ADDR not being called. When the > printk was added by commit 776e58ea3d37 ("KVM: unbreak userspace that does > not sets tss address"), KVM also stuffed a "hopefully safe" value, i.e. > the message wasn't purely informational. For reasons unknown, ostensibly > to try and help people running outdated qemu-kvm versions, the message got > left behind when KVM's stuffing was removed by commit 4918c6ca6838 > ("KVM: VMX: Require KVM_SET_TSS_ADDR being called prior to running a VCPU"). > > [...] Applied to kvm-x86 vmx, thanks! [1/1] KVM: VMX: Delete ancient pr_warn() about KVM_SET_TSS_ADDR not being set https://github.com/kvm-x86/linux/commit/9ca0c1a1265c -- https://github.com/kvm-x86/linux/tree/next https://github.com/kvm-x86/linux/tree/fixes