From nobody Tue Apr 7 07:05:57 2026 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 D5505ECAAD5 for ; Wed, 31 Aug 2022 00:17:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231641AbiHaART (ORCPT ); Tue, 30 Aug 2022 20:17:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54638 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231185AbiHaARL (ORCPT ); Tue, 30 Aug 2022 20:17:11 -0400 Received: from mail-pg1-x549.google.com (mail-pg1-x549.google.com [IPv6:2607:f8b0:4864:20::549]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1469997D6A for ; Tue, 30 Aug 2022 17:17:11 -0700 (PDT) Received: by mail-pg1-x549.google.com with SMTP id a33-20020a630b61000000b00429d91cc649so6177533pgl.8 for ; Tue, 30 Aug 2022 17:17:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:reply-to:from:to:cc; bh=inZmAldSU4aSVbi2qd8QeS7mQNQRQnMt4A+ie/z8kT4=; b=fw5mYkkDqyqthv1ZRUQttXv6Rt6nsjmDZuPEL/hSLeU1qHD2O7Pudcyzxr1Eltpwap VBveF2fI4xy3WgARvDqfhk0cGTyAXcKDKfw/2X4eyn8teb5Ig6p233OlvrtBmpJ6u7wE yi/6ALf7NqSqSQJgVbppcAeu779Yn5Q4M74lunps77pzDcx4J8XThFxm7itG8VnqOpUP 7dgZGNhCGoY3KrB4T3RR+dL0APKedZRNaunchY5WFgIexJPp8YDEMIjElBU7XgOWewQ1 H2EwW7vghCKWVrW3jsE1i6ipr0jNdm3vAddWKajWAloOh7Qg3MpBy9Z3O5z40P0xSqAl CUHQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:reply-to:x-gm-message-state:from:to:cc; bh=inZmAldSU4aSVbi2qd8QeS7mQNQRQnMt4A+ie/z8kT4=; b=5Z8ZqQr4MAggz3Pa7DYFOe5VTIpBTv3Vg4/BcfEi9wxYn1AZ0fc/S4MnCCuH+f5Bze VK+P5ZGCGBFbmUPkfFdq+wYstARwPda2AM+kuWbmHLmrdU366GZ8uReBWpnX40VwaZGo 6Zd5KrTqP0WiQjfT9x/mq762SWyxp2DCWnZngm5omjIBD9UD+TWEN90vvWtUiQn6UxyF qM6qCONh8n+VPfgn6p5cTGL6Xuhp4ssswrjplLRur3bsNkSG0SLeEedbewjtpqWt+VbO p0uW6LVxPBQFuCsZT9kEsxZEVzXEtXo6VSAEyUlBCp/0Tk4B5naB7APCBNkOm4eG7E/Y MpHA== X-Gm-Message-State: ACgBeo3oq40Pw2i6kyT2AAdj2wOCagPPd1xtRXG9SHC+UoCUXiZlgSuW t/LAbSn/zp3RWzc1oX6c/1v8HaLSQPs= X-Google-Smtp-Source: AA6agR61rRRBtVSh/bqQGKudwNlbYfL17nqG83gwCw/bfIDZc5+kB//aIfVhaX+yuKKqFlBUleMQAN1NbAM= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:902:edc3:b0:172:8ae3:9778 with SMTP id q3-20020a170902edc300b001728ae39778mr23098814plk.72.1661905030673; Tue, 30 Aug 2022 17:17:10 -0700 (PDT) Reply-To: Sean Christopherson Date: Wed, 31 Aug 2022 00:17:04 +0000 In-Reply-To: <20220831001706.4075399-1-seanjc@google.com> Mime-Version: 1.0 References: <20220831001706.4075399-1-seanjc@google.com> X-Mailer: git-send-email 2.37.2.672.g94769d06f0-goog Message-ID: <20220831001706.4075399-2-seanjc@google.com> Subject: [PATCH 1/3] KVM: x86: Delete documentation for READ|WRITE in KVM_X86_SET_MSR_FILTER From: Sean Christopherson To: Paolo Bonzini Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Sean Christopherson , Aaron Lewis Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" Delete the paragraph that describes the behavior when both KVM_MSR_FILTER_READ | KVM_MSR_FILTER_WRITE are set for a range. There is nothing special about KVM's handling of this combination, whereas explicitly documenting the combination suggests that there is some magic behavior the user needs to be aware of. Signed-off-by: Sean Christopherson --- Documentation/virt/kvm/api.rst | 7 ------- 1 file changed, 7 deletions(-) diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst index 236a797be71c..5148b431ed13 100644 --- a/Documentation/virt/kvm/api.rst +++ b/Documentation/virt/kvm/api.rst @@ -4115,13 +4115,6 @@ flags values for ``struct kvm_msr_filter_range``: a write for a particular MSR should be handled regardless of the default filter action. =20 -``KVM_MSR_FILTER_READ | KVM_MSR_FILTER_WRITE`` - - Filter both read and write accesses to MSRs using the given bitmap. A 0 - in the bitmap indicates that both reads and writes should immediately fa= il, - while a 1 indicates that reads and writes for a particular MSR are not - filtered by this range. - flags values for ``struct kvm_msr_filter``: =20 ``KVM_MSR_FILTER_DEFAULT_ALLOW`` --=20 2.37.2.672.g94769d06f0-goog