Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:6 as permitted sender) client-ip=2620:137:e000::3:6;
Date:   Thu, 30 Nov 2023 17:52:08 -0800
In-Reply-To: <20230315101606.10636-1-wei.w.wang@intel.com>
Mime-Version: 1.0
References: <20230315101606.10636-1-wei.w.wang@intel.com>
Message-ID: <170137868908.667071.11420459240927661184.b4-ty@google.com>
Subject: Re: [PATCH RESEND v2] KVM: move KVM_CAP_DEVICE_CTRL to the generic check
From:   Sean Christopherson <seanjc@google.com>
To:     Sean Christopherson <seanjc@google.com>, pbonzini@redhat.com,
        Wei Wang <wei.w.wang@intel.com>
Cc:     kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="utf-8"
Precedence: bulk

On Wed, 15 Mar 2023 18:16:06 +0800, Wei Wang wrote:
> KVM_CAP_DEVICE_CTRL allows userspace to check if the kvm_device
> framework (e.g. KVM_CREATE_DEVICE) is supported by KVM. Move
> KVM_CAP_DEVICE_CTRL to the generic check for the two reasons:
> 1) it already supports arch agnostic usages (i.e. KVM_DEV_TYPE_VFIO).
> For example, userspace VFIO implementation may needs to create
> KVM_DEV_TYPE_VFIO on x86, riscv, or arm etc. It is simpler to have it
> checked at the generic code than at each arch's code.
> 2) KVM_CREATE_DEVICE has been added to the generic code.
> 
> [...]

Applied to kvm-x86 generic, thanks!

[1/1] KVM: move KVM_CAP_DEVICE_CTRL to the generic check
      https://github.com/kvm-x86/linux/commit/63912245c19d

--
https://github.com/kvm-x86/linux/tree/next